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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I have renamed an issue type but it is not updating in the issue type scheme. What do I need to do to update it correctly?
Hi Michelle,
This is a bug in jira and reported by several users. I myself faced this issue sometimes ago in jira service desk. Below is a workaround to resolve this which i found in some discussion earlier.
Go to Jira settings > Issues > Issue Type schemes > Edit the desired scheme > drag and drop affected Issue type somewhere up or down on the list and then save the configuration. The Issue type can now be moved to the original position if required.
Regards,
Rakesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm posting a question on this thread, but understand if its too old to get a response. Using our test environment, I followed instructions to rename "epic" to "feature". worked as expected. We changed it back to "epic" and ran into an issue with the "epic name" not showing in the epic link field of a child story. This only occurs on epics and stories that are created post 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". The intent is to associate with the epic issuetype, however it is locked. Has anyone run into this scenario?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Are you on Server or Cloud? If the former, can you try and run a full foreground index by going to Settings > System > Indexing > Full re-index > Re-index
Re,
Kuherrn
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, folks. Here's the link to the bug that was created regarding this:
After an issue type is renamed, the new name does not display for edit, create, or edit issue type in the View Issue screen
Take the time click "This affects my team" if that's the case!
Cheers,
Filipi Lima
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Michelle Greenfield since you posted in the Jira Service Desk forum I need to ask if you've updated the request type or issue type.
If you are aware of the difference between the 2 then I'd ask to check issue - issue type scheme association .
If you've done all of that but still have no success could you post a few screenshots ( anonymised of course) so I can take a look?
Thanks,
Radu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.