We've just introduced Epics to next-gen Software projects and with that comes a new way to manage them: the Roadmap. This represents a huge and exciting change in how Epics are managed in Jira Software Cloud. We believe this will be an easier way to manage and visualize your epics and would love to hear what you think about it.
This tutorial explains how epics generally fit into the agile development process and shows how to work with epics in next-gen projects to help you with your next big project.
What's the difference between epics and other issue types?
Stories, bugs, and tasks are used to describe one single piece of work, while epics are used to describe a group of issues that all relate to the same, larger body of work. Epics are typically completed over several sprints, or a longer time frame if you don't use sprints. Check out our guide on delivery vehicles for more info.
Epics are created and managed in the Roadmap. The Roadmap is useful for visualizing and planning large pieces of work that may be in progress right now or you may prioritize in the future.
When should I create an epic?
Consider creating an epic if you have a large body of work that needs to be completed over several sprints or over a long period of time. You could also create an epic if you notice a pattern amongst several user stories you've created, and you want to bundle them into one group.
In the project menu, select Roadmap.
Pro tip: Outside the Roadmap, you can also create epics from the global menu.
Drag the edges of an epic's bar to modify its start and due dates. You can also edit these dates by clicking an epic and opening its details. You don't have to set start and due dates, but we recommend you do to make long-term planning easier.
To add issues from the board and backlog:
On the Board
On the Backlog
To add issues to an epic from the roadmap:
Pro tip: You can select multiple issues with Command + Click on Mac or Ctrl + Click on Windows, and add them all to an epic at the same time.
You can view an epic's details, like start date, due date, and child issues by selecting it on the Roadmap.
During a sprint, you might find it useful to divide your board into swimlanes for each epic, to easily visualize your progress. To set this up in your next-gen Software project:
Pro tip: You can create issues under an epic swimlane to quickly add a new issue to an epic. This also works if you've selected an epic in your filter.
Once all the work for an epic is completed, you should mark it as complete on the roadmap.
To complete an epic:
Select the epic you'd like to mark as complete.
Under Status, select Done.
When should I mark an epic as done?
Mark your epic as done whenever all work for the epic is complete. To make this easier, we recommend coming up with a clear definition of done for your epic when you create it.
Kevin BuiAtlassian Team
Do you have a hard time meeting sprint commitments? Do you want to know the accuracy of your sprint’s estimations? Do you want to have an easy way to report your team...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events