Hi Jira Community!
We want Jira to be able to reflect the way teams work, no matter what framework you may or may not use. That’s why we’re looking at providing you with the flexibility to shape our tools to the way you work, starting with the name of your epics in your company-managed projects.
Why start here? We know many teams using Safe Agile Framework (SAFe) struggle because they’re unable to reflect their issue hierarchy in Jira Software Cloud, namely Features as the parent of stories, rather than epics. Non-software teams can also benefit from terminology that better reflects their work, e.g. campaign, candidate, etc.
We hope that these changes will be valuable for all teams, providing you with more control of your issue hierarchy and the epics in your Jira site.
Issue hierarchy configuration will soon have a new home in the global Jira admin settings. This means that teams using Free and Standard Jira will now have the ability to manage their issue hierarchy, up to the epic level.
You’ll be able to access this new settings screen by heading to: ⚙️ Settings > Issues > Issue hierarchy.
What does this mean for you? On this screen, you’ll be able to rename and add issue types to the epic level in your site’s issue hierarchy.
And, changing the name of your epic level is easy! Just click the level name (by default, this will be Epic), type in a new name, and hit Save changes.
Once you’ve changed the epic level name, head over to the Issue types settings screen, and update the name of the Epic issue type to reflect your new level name.
Changes you make to your epic level will be reflected throughout all company-managed projects in your site. For example, if you’ve renamed the epic level to Feature, your backlog will now contain a Feature panel, rather than the existing Epic panel.
Note: As part of these updates, only issue types on the base-level (that’s the default level for stories, tasks and bugs) can have an epic as their parent.
If you’re an Advanced Roadmaps user that has epic links for issues above the epic level, you’ll need to update these epic links by
Feb 1st, 2022 April 1st, 2022 to ensure this relationship data is not lost. Visit our guide to find out if you're affected and learn what you need to do to maintain your data.
Alongside these updates, we’re making additional changes on the board and backlog to more closely align epics across company-managed and team-managed projects:
The epic color on the board and backlog will now use the epic’s Issue color.
The name of the epic on the board and backlog will now use the epic’s Issue summary.
What does this mean for you? Well, depending on how they’re set up, your epics might look a little different when viewing them on the board and backlog.
For example, issues on your board and backlog will now use the epic’s Issue summary in their lozenge. If the name of your epic and its issue summary are different, then these lozenges will be updated when we roll out these changes.
We’re improving the way you associate epics with your bugs, stories and tasks in the issue view. Currently, this is done via your issue’s Epic link field – we’ll soon be replacing this with a new Add parent feature.
We’ve heard from you that the location of the Epic link field in the issue view can make it difficult to add epics efficiently, so we’re adding the ability to add a parent directly from your issue’s breadcrumb, consistent with how you work in team-managed projects.
You’ll also be able to add a parent from the Actions (...) menu or using keyboard shortcuts.
To reflect these updates, we’re also making some small changes to our JQL functions. The parent() JQL function will extend to incorporate the functionality of the “epic link”, “parent link” and “parentEpic” functions.
While these functions will continue to work and new ones can be created in your JQL searches, we’ll be removing them from auto-complete and encouraging teams to use the parent() JQL function.
We’re currently working at building out these new experiences in your company-managed projects. Our updates are scheduled to begin rolling out from mid-2022. Keep an eye out here on the Atlassian Community for more news closer to our release date.
In the mean time, we’d love to hear your thoughts on these updates, so let us know your feedback and suggestions in the comments below. Thanks!
Rohan SwamiAtlassian 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