Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,364,036
Community Members
 
Community Events
168
Community Groups

Change the issue type Epic to Feature

I heard from a developer that the Epic name could be changed to Feature without installing a plugin.  Please advise if this is possible on the Server or data center.  

kind regards. 
kendall

1 answer

1 accepted

3 votes
Answer accepted
Pramodh M Community Leader Aug 25, 2022

Hi @Kendall Alton 

It's not the best practice to edit the Epic Issue type to something else as it has a meaning which is used universally in Agile world and if you still want to change the Issue type name here is the guide to rename the Epic Issue type

https://support.atlassian.com/jira-cloud-administration/docs/add-edit-and-delete-an-issue-type/

The navigation is same 

Cog Icon, Issues, Issue types, Select the issue type you want to rename and edit it

Once you rename it you may need to follow this guide to see the changes 

https://community.atlassian.com/t5/Jira-Service-Management/Renaming-Issue-Type/qaq-p/1180192

Let me know if you have any query 

Thanks,

Pramodh

Pramodh M, your solution worked, thank you. The change require both steps to complete the update.  I’m testing edge use cases in the dev environment to ensure all works as expected, but no issues found at this point.  There is likely a reason the issuetype  description has a comment of “do not edit”, but cautiously optimistic for this solution.  

thank you!

K

@Pramodh M update: I followed instructions to rename "epic" to "feature".  worked as expected.  We changed it back to "epic" in our test environment, as conducting Align integration testing.  After reverting the change back to "epic", we found that the the "epic name" not showing in the epic link field of a child story.   This only occurs on epics and stories that are created after the rename.   The view and edit schemes of the epic no longer include the "epic name" field, so followed the dialog to the "configure Custom Field: Epic Name" to update the context in order to associate the field back with the epic issuetype, however it is locked.   Has anyone run into this scenario?

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events