Until ~2018 we used Sprintr for stories and sprints, but with a 10-year history it became unbearably slow. Then we first used a free alternative and now Jira for a few years. In the meantime Mendix has come up with Epics. It looks promising and useful, since were not exactly power users or Jira enthusiasts, although we are set in our ways. Now my question is: what experience do you have with Epics and how does it compare to Jira? Are there features from Jira you (would) miss in what Mendix has to offer? Or do you have other insights that relate to our use case (see requirements below)? (Btw, I'm also doing my own research ofc, but I'm curious how the community sees this and what real world experience you have with it.) What we use: - epics, stories, backlog, sprints, sprint planning, board with swimlanes - commenting system to discuss items and tag each other, resulting in email and/or Slack notifications (Sprintr used to send a daily recap iirc, maybe Epics has that too, which would also be fine I guess) - flags to mark items for discussion at earliest convenience (the refinement section in Planning seems like a good or even better alternative) What we don't use: - project management or progress tracking - Jira tools for documentation, project pages, Confluence etc - story points, sprint poker etc - integration with Studio Pro, coupling with branches or commits - feedback widget to automatically send items by end users from within an application into the backlog or whatever for that project What might be challenging: - we have a small team, but multiple Mendix applications that we all work on, so we would either need sprints or boards to allow for combining stories from different projects, or we would have to choose one project in which we keep all epics and stories. Thanks in advance for your insights.