Upcoming - Rename ‘epics’ in your company-managed projects

[#1]

Updated February 2023: The functionality outlined below in this post is not yet available. We’re currently working at building out these new experiences and will provide additional updates as we get closer to our release date. You can follow the projected GA release date on the cloud roadmap.

---

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.

Manage issue hierarchy in your admin settings

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 July 5th October 31st, 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.

Changes to epics on your board and backlog

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.

Updates to your issue view

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 in your existing JQL searches, you’ll no longer be able to use them in new searches. Instead, teams should begin using the parent() JQL function.

What’s next?

We’re currently working on building out these new experiences in your company-managed projects, and will provide additional updates as we get closer to our release date. You can follow the projected GA release date on the cloud roadmap. 

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!

FAQ

Q: Can I create issues above the epic level in the issue hierarchy as part of these changes?

A: This feature is currently available for customers on Premium or Enterprise plans.

Q: Where can customers on Premium plans find their hierarchy configuration now?

A: To view the existing hierarchy configuration: In the navigation bar, go to Plans > Settings, and then select Advanced Roadmaps hierarchy configuration from the sidebar.

Q: Will the Advanced Roadmap hierarchy configuration continue to be available when these changes roll out?

A: These changes will combine the existing Advanced Roadmap hierarchy with Jira’s issue hierarchy.

The existing configuration screen in the Advanced Roadmaps settings will redirect you to its new home in the global Jira admin settings.

Q: Will these changes impact how I can edit the levels below epic?

A: Levels below the epic level are unaffected by these changes.

Q: How will these changes impact my automation rules?

A: These changes will affect rules using the following smart value properties:

• Epic Link

• epic

• Parent Link

Atlassian plans to migrate the affected smart values by 31 May 2022 so that Automation rules won’t break. If there are any edge cases we're unable to migrate, we'll communicate this closer to the time.

Q: Will it be possible to rename epics in Jira Server or Data Center products as well?

A: For information on configuring flexible terminology in for Jira Software Data Center, see:

• https://confluence.atlassian.com/adminjiraserver0817/configuring-terminology-1071816868.html

Q: Will there be any impact on the epic panel?

A: The epic panel will respect any changes you make to your epic level name. Listed epics will also begin using their Issue summary. Learn more about these changes.

Q: Do you have more information around the changes to the epic name and epic color?

A: These updates are designed to reduce the use of epic fields in Jira experiences. No existing data in these fields will be lost. Learn more about these changes.

Q: How will this impact queries and reports?

A: Queries and reports will be unaffected by these changes.

Q: Will the portfolioChildIssuesOf function continue to work as part of these changes?

A: The portfolioChildIssuesOf function will be unaffected by the changes.

[Nikki Zavadska _Appfire_]

Thank you for the heads up @Rohan Swami ! I'm curious, with all these changes are you also planning to introduce the ability to create issues above epics in the hierarchy?

For example:

- Initiative
-- Epic

---Story

---Subtask

[Rohan Swami]

Hi @Nikki Zavadska _Appfire_ these levels above Epic can be created now in Premium.

[Maite Rodriguez]

Hi @Rohan Swami1,

I have 2 questions about this:

I have a dozens of automations based on epics. How will this change affect their perfomance?

I'm already using roadmaps and its hierarchy:

 Initiative

Epic

Story

Sub-task

but currently I can't edit the levels below epics, I'd need to be able to link subtasks to user stories in different Jira projects . Is this contemplated with this new change?

Thank you!

[Charlie Gavey]

Hi @Maite Rodriguez

If you use the "Epic Link", "epic", or "Parent Link" fields in Jira Automation’s smart values, you may be affected by this change.

Atlassian plans to migrate the affected smart values by 31 May 2022 so that existing Automation rules won’t break, meaning you shouldn't need to make any changes on your side. If there are any edge cases we're unable to migrate, we'll communicate this closer to the time.

Cheers,

Charlie

[Maite Rodriguez]

Hi Charlie,

Thank you for your response. I have a question about it:

You said that: "Atlassian plans to migrate the affected smart values by 31 May 2022 so that existing Automation rules won’t break " but this implementation will be released on Feb 1st, 2022. 

Therefore, during that month, our rules will not work?

Thank you very much.

Cheers,

Maite

[Ravi Sagar _Sparxsys_]

This was very much needed. Thanks for the update. 

[Rohan Swami]

@Maite Rodriguez Automation for epic links, parent links and epics will continue to work between Feb and May. It is only invalid epic link data that is affected from Feb 1, more details are here https://support.atlassian.com/jira-software-cloud/docs/maintain-epic-link-data-for-issues-above-the-epic-level/

In response to your other question, levels below Epic are unaffected.

[Sebastian Mühleis]

Hello @Rohan Swami ,

first of all thanks for these exciting news. Now to my question:

Where can I find the hierarchy levels in Premium? Or is this feature solely for Free and Standard plans?

I'm pretty sure I've already set hierarchy levels (with Initiative above Epic), but right now I can't find it the way you showed it.

Thanks in advance and all the best,

Sebastian

[Maite Rodriguez]

Hi Rohan Swami,

Thank you for your response.

When you say "levels below Epic are unaffected."  Does it means that we'll not have the functionality to modify the hierarchy below epics (I think about subtasks in several projects linked to the same user story) .

Thank you!

[Rohan Swami]

@Maite The subtask issue type can not be moved to another level and will not after these changes are rolled out. Sub-tasks can be moved to another project but the parent must be in the same project.

@Sebastian Mühleis The hierarchy levels can be found by navigating to Plans (in the top nav) > Settings > Advanced Roadmaps hierarchy configuration. The screens on this blog show the future state after the changes are rolled out.

[Maite Rodriguez]

Hi @Rohan Swami ,

Thank you for your response. I have a question about it. You said: 

"Sub-tasks can have a parent in another project and will continue to be able to after these changes are rolled out."

But currently,  I haven’t be able to linked a sub-tasks with a parent in another Project. I only can related a sub-task with a task in the same Project. Can you confirm this and tell me how to do it?

Thank you very much.

Cheers,

Maite

[Rohan Swami]

@Maite Rodriguez I've corrected that: Sub-tasks can only have a parent in their current project.

[Kari]

@Rohan Swami 

Hi Rohan, 

Great News!

Will it be possible to Rename ‘epics’ in Jira Server as well? 

Cheers,

Kari

[Christina Robinson]

How will this functionality work on importing? Both to create the Epic (Feature) as well as creating the relationship child relationships between base items under Epics.

Also, is there a reason that the items like Epic Name, Epic Link, Epic Status, and Epic Color fields wouldn't just translate it to say Feature Name, Feature Link, Feature Status, and Feature Color respectively? 

I'm also a little curious in how it works in regards to utilizing JQL for searching for the Epics. :)

Thanks,

Christina

[Rohan Swami]

@Christina Robinson We've chosen this approach because it allows us to support multiple issue types at the Epic level in the future. Hierarchy config settings apply to the collection of issue types at that level, and Issue Types config applies to the Epic issue type specifically. The parent JQL function will replace the current functions for searching for Epics, though the current functions will continue to work.

@Kari please find details here on implementation in Data Center:
https://www.atlassian.com/blog/jira-software/flexible-terminology-for-jira-data-center
https://confluence.atlassian.com/adminjiraserver0817/configuring-terminology-1071816868.html

[Nigel Budd]

Am really looking forward to this feature.
I would have liked to see the free/standard tiers support a hierarchy above Epic as managing hierarchies is currently a weak area of Jira.  I do understand that this is mostly needed by larger companies and that those are most likely to have Premium, but I think it would make consistency between your tiers easier if the hierarchy could be configured on all tiers.

I would also like the AR hierarchy and Issue hierarchy to be combined, it wasn't clear to me whether AR hierarchies would also continue after this feature is rolled out.

[Kelly McConnell]

@Rohan Swami Thank you for the great summary above. Where can I find more granular release info for Jira Cloud beyond the Q2-Q3 date given for "Flexible naming of Epics" in the Product Roadmap for Jira Cloud?

There are smaller changes you detailed above which are not mentioned on that high level roadmap that my team needs for a near term change we making using Forms in a Work Management project. The particular update I am interested in is the consolidation of the epic's name and summary into just the epic's summary since the epic name is not a supported field in Forms.

[Rohan Swami]

@Nigel Budd Thanks for the feedback on our edition-gating. The AR hierarchy and Issue hierarchy will indeed be combined as part of this work.

@Kelly McConnell we'll be sharing details on our plans for the Epic name/summary fields well ahead of the release. For now, I can say that we'll reduce the usage of the Epic fields in Jira experiences, and no data will be lost from those fields.

[Maite Rodriguez]

Hi @Rohan Swami

Thinking about this topic, I have a new question: will the function portfolioChildIssuesOf be working after the change? I'm using it to know all the issues in a Initiative,  and my link between Initiative and task is  the epic.

Thank you. Regards.

[Rohan Swami]

@Maite Rodriguez portfolioChildIssuesOf will be unaffected by the changes.

[Paula Hidalgo]

I don't understand what you mean by the statement below.  If the field Summary != Custom field (Epic Name), will the Summary field or the Epic Name field be retained?  (According to dictionary.com, a lozenges is a diamond shape)

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.

[Julia Foden]

Hi @Rohan Swami 

You said that the parent() JQL function will incorporate the functionality of "parent link". However there is a bug with "parent link" in that certain usages of it time out and are impossible to use. See https://jira.atlassian.com/browse/JSWCLOUD-21810 

Will parent() solve this problem? 

[Coco S Chaussée]

That is great news!

How will this impact queries and reports?

[Maite Rodriguez]

Hi @Rohan Swami ,

I have another question about this change. In the configuration board, there is the option to configure Epic panel.  What will be the behavior of this after the change?

Thank you very much! 

[Rohan Swami]

@Paula Hidalgo The Epic Name field will still exist. The change that we are making is that the lozenges in the board/backlog will use the Issue Summary instead of the Epic Name. In the example below the Epic Name is Accounts, if the Issue Summary was The Accounts Team, the blue lozenges would update to The Accounts Team when we roll out the change. 

@Julia Foden I expect that the parent() JQL function won't inherit the bug from parent-link JQL.

@Coco S Chaussée Queries and reports should be unaffected.

@Maite Rodriguez There will be some minor changes to Epic Panels, we'll provide these details in a dedicated blog post. Similar to the changes we've discussed here it will also change to using the Issue Summary.