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.
@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?
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!
We often have questions from folks using Jira Service Management about the benefits to using Premium. Check out this video to learn how you can unlock even more value in our Premium plan. &nb...
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