Epic rename to Features when?

[Eric Roetenberg]

Hi,

I read the following message on the atlassian site from when will we be able to use Jira Cloud. Epic to Features and will filters etc be automatically adjusted?

https://community.atlassian.com/t5/Jira-articles/Rename-epics-in-your-company-managed-projects/ba-p/1874726

[Nic Brough -Adaptavist-]

It'll be rolled out across all Cloud sites by 1st April, according to the docs.

Filters should not be affected, they don't really use the name of the issue type.

[Eric Roetenberg]

@Nic Brough -Adaptavist- Is there anything known yet if this will go ahead, where can I find information about this.

[Nic Brough -Adaptavist-]

It's happening already, the Cloud sites I've got access to at the moment all have it.  Atlassian don't give dates for individual sites, all I can tell you is that everyone should have it before the end of this month.

[Eric Roetenberg]

Hello Nic , do you have a print screen 

[Eric Roetenberg]

Hello Nic

I hope it is not an April 1 joke our whole organization is waiting for it and we have taken it into account with several projects it will cost a lot of money if it does not go through.

[Nic Brough -Adaptavist-]

From the Community Leader's sandbox (which I think is way up the "get the new stuff" list, so we get to be able to play with it for helping other people early)

[Eric Roetenberg]

Hi, but this is premium and the customization would be for Jira cloud standard

[Nic Brough -Adaptavist-]

Yes, that's what the doc did say.   Apparently, standard doesn't need to rename Epics, as it's not doing SAFe (although you can rename them, it's just the disconnect between "Feature" and Epic report/name/colour etc that will need you to talk to people about)

[Eric Roetenberg]

Hi Nic

I don't have a Issue Hierarchie button. what can i do ?

[Nic Brough -Adaptavist-]

You'll need to go up to premium to get Advanced Roadmaps I'm afraid.

Standard Jira only supports three levels of issues, and doesn't have the functions to rename Epic-things on view if you rename the Epic to something else (but renaming Epic to Feature will no longer break anything other than the human "why are my reports still called Epic reports when the issues are now called 'features'")