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.
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.
Hi everyone! Are you interested in beta testing Atlassian University’s newest (unreleased!) training course? We’re looking for 15-20 volunteers to test our newest training course, Basic reporting...
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