It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Will renaming the "Epic" issue type, "Retainer" issue type cause confusion?

I have been asked to rename the Epic issue type to Retainer. I am concerned that if I do that it will cause confusion for users with regards to Epic name, link, color and status. 

Can I rename Epic name, link, color and status. to be Retainer name, link, color and status.?

1 answer

1 accepted

1 vote
Answer accepted
Jack Community Leader Sep 17, 2019

You can’t change the system field names. And why “retainer” which is something that holds something in place while an epic, in scrum terms, is a collection of stories.

It is possible to unlock and rename the fields on a Server/DC install, but it is not a good idea.  Apart from "retainer" really not meaning the same things as what an "epic" is for and hence confusing people:

Jira is now quite widely used, and people coming from an environment that has Epics will find it very strange

While I've not run into problems with renaming Epic in an off-the-shelf Jira, it causes havoc with some apps, including some Atlassian ones! (and completely rules you out of ever using Align, I learned a few weeks ago)

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira

Demo Den Ep. 7: New Jira Cloud Reports

Learn how to use two new reports for next-gen projects in Jira Cloud:  Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...

314 views 1 3
Join discussion

Community Events

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

Events near you