Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-23148

Updating the name of a Global Issue Type does not update it's name across any Issue Type Schemes it may be associated with

XMLWordPrintable

      Steps to reproduce:

      1. Administration > Issue Types
      2. Rename 'New Feature' to 'Blahhh'
      3. Switch to 'Issue Types Scheme' tab
      4. Notice that the old name still exists

      This affects the GUI in various other locations and is causing some confusion among users. Restarting JIRA fixes it.

      Alternative workaround: click "edit" next to the affected issue type scheme, then save it without making any change. The issue types contained in the issue type scheme will now be updated with the correct values

            [JRASERVER-23148] Updating the name of a Global Issue Type does not update it's name across any Issue Type Schemes it may be associated with

            Noel Dinger added a comment -

            Got this issue in Jira Software 8.5.1

            Noel Dinger added a comment - Got this issue in Jira Software 8.5.1

            Matt Doar added a comment -

            There's a workaround in a comment on JRASERVER-64106

            Matt Doar added a comment - There's a workaround in a comment on  JRASERVER-64106

            Jeff Louwerse added a comment -

            Thanks Tarun.. that worked perfectly.  I have created REST interfaces to clear all the other caches that Jira holds onto forever but this one didn't seem to have an easy way to clear it.  Setting and resetting the default Issue type worked great.  

            Jeff Louwerse added a comment - Thanks Tarun.. that worked perfectly.  I have created REST interfaces to clear all the other caches that Jira holds onto forever but this one didn't seem to have an easy way to clear it.  Setting and resetting the default Issue type worked great.  

            David Phillips added a comment -

            I've noticed something similar When updating a screen scheme to use a new screen the change reflects for me (admin) but not for other uses. However, after a little time passed the change DID appear for the other users. Same thing happen for you guys? @sapra97 @majken

            David Phillips added a comment - I've noticed something similar When updating a screen scheme to use a new screen the change reflects for me (admin) but not for other uses. However, after a little time passed the change DID appear for the other users. Same thing happen for you guys? @sapra97 @majken

            Tarun Sapra added a comment -

            Indeed this is an issue, we also faced it today , 7.3.0 JIRA Software. A quick way to fix it is to make the issueType the "default" in the issueType Screen scheme and then revert back to the old default. This somehow refreshes the cache of the create issue popup and it starts displaying the new name of the issuetype instead of the old cached named.

            Tarun Sapra added a comment - Indeed this is an issue, we also faced it today , 7.3.0 JIRA Software. A quick way to fix it is to make the issueType the "default" in the issueType Screen scheme and then revert back to the old default. This somehow refreshes the cache of the create issue popup and it starts displaying the new name of the issuetype instead of the old cached named.

            Majken Connor added a comment - - edited

            Just hit this issue for the first time, setting up a new JIRA Software server instance, v7.3.8

             

            It also doesn't update in the create issue button, trying to create an issue with the old information just closes the create screen. <-- This was when creating from the admin panel, ie you pick project and issue type and click next, but we can't reproduce it anymore

            Majken Connor added a comment - - edited Just hit this issue for the first time, setting up a new JIRA Software server instance, v7.3.8   It also doesn't update in the create issue button, trying to create an issue with the old information just closes the create screen. <-- This was when creating from the admin panel, ie you pick project and issue type and click next, but we can't reproduce it anymore

              Unassigned Unassigned
              mtaylor@atlassian.com Maleko Taylor (Inactive)
              Affected customers:
              11 This affects my team
              Watchers:
              19 Start watching this issue

                Created:
                Updated: