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
Technically, yes, but when you go to do it, you will find a warning not to.
Heed that warning - it breaks a lot of things in interesting ways when Epics are not named "Epic"
Atlassian do have an open and active development task on allowing it to be done, as Align needs it to be Feature instead of Epic as well, but until that is implemented, don't.
i wish they would disallow until they could support unconditionally. and i don't think they should allow renaming but rather allow adding a new issuetype of type Epic.
We have been looking into doing this - changing our 'Epic' field name to 'Feature'. However, it is looking way to messy. We now have locked fields for 'Epic Name' which would not be able to change with the field rename - as well as the Epic Link which is also a locked field for us. We also have Script Runner scripts which utilize the 'Epic' field name. So even though from a Scaled Agile perspective it makes more sense to go Epic->Feature->User Story->Task, thanks to this setup (which apparently ignores the Scaled Agile process), we will need to work around it and maintain the Epic field in JIRA.
TBH, I have never tried and I have always understood (?) it cannot be done. However, you can try here > admin > issues > issue types, find Epic and click edit? I don't have a test instance where I could try it. Let me know.
Hi @Sara Creenan (M&T) ,
But after rename, this is not impacted in Epic panel and Epic link field and some other places.
If you have many projects , this will impact all the others.
Please rethink once again before proceeding