You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We have recently adopted Jira Align.
We are having issues with the terminology from a user perspective, it is a source of confusion...
In Jira Cloud the issue type is called "Epic".
We have updated the terminology in Jira Align to read "Features (Jira Epics)".
Is there a way to rename the issue type "Epic" in Jira Cloud to say "Feature"?
What's the experience and recommendations from the community on this topic?
Great questions @Aline Chapman ! If you're using Jira Cloud you can easily do this. When you go into Jira Admin > Issues > Issue Types you can simply rename the Epic issue type to Feature.
The one nuance with this that I have found is that it doesn't change the name of the Epic Link and Epic Name custom fields in Jira. This means that the issue type will now be "Feature" but those two fields will still contain the word "Epic" in them. There might be a way using some scripting to correct this, but I haven't come across it.
There is no way to fix the names of fields, and that naming problem extends to things like the gadget names, epic reports and so-on.
The use of "Epic" throughout Jira is endemic, and can't (yet) be changed. If you rename it to Feature, the issue (type) will work fine, but all the language will be confusing throughout!
@Aline Chapman It is possible to rename "Epic" issue type to "Feature" in Jira Cloud via Administration->Issues->Issue Types->Epic; click on three dots, which shows "Edit". In order to do that one should have Jira Admin access. Renaming is a global change (Configuration), it would impact all Jira projects in that Jira Cloud instance.
In my experience, organizations don't prefer to rename "Epic" to "Feature" in Jira. However, it requires good communication to the teams not to confuse it with Jira Align Epic.
It works fine with single NextGen projects (team managed). With classic projects (company managed) the change is globally for all classic projects. In the following example I renamed "Epic" to "Konfektionierung" for a NextGen project.
You may also wanna have a look at Custom Epic Panel | Atlassian Marketplace.
It will work fine, with three caveats.
The first two points stand. On the third one, if you have Advanced Roadmaps and you rename Epic in the hierarchy in there, then the cosmetic details do now change.
@Nic Brough -Adaptavist- Just updated the Issue Type name in a test environment, "Epic -> Feature". After this, updated the Level name in Roadmaps also to "Feature", and still see the fields being labeled as "Epic Name".
Is this what you meant above? Is there another step to get these fields updated? Or is there a specific Data Center Version you need to be on?
Yep, you can do it with Advanced Roadmaps now. Not entirely sure what the exact version it arrived in, but you are definitely good from 9.0 onwards.
Currently testing on v8.20.12. Did the updates and now doing a full system reindex. Wasn't seeing the updates flow through to the custom fields. Is there a step I could have missed?
Found that this needs to be done from the terminology section of the app. Once you do it there it does the updates successfully.