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

Renaming Priority, Resolution, Status, Issue Type does not get reflected until a system restart

    XMLWordPrintable

Details

    Description

      When you change the name of a priority, status, resolution or status we do not call refresh for their caches and they become stale.
      This affects places that use the Objects rather than the genericValues.
      The changes are only reflected once you restart the system.

      See AbstractEditConstant.doExecute()
      This should either call an abstract method that just clears that Constants cache or it could just call DefaultConstantManager.refresh()

      Attachments

        Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-22219 In Workflow used status is not updated after renaming the status itself

          • Low - Low priority issues
          • Closed
          details

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-23197 remove note about restart when renaming a Priority (when JRA-23196 is fixed in 4.2.2)

          • Low - Low priority issues
          • Closed
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-22637 Issue status modifications do not reflect in workflow steps and issue navigator search terms

          • Medium - Medium priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-22749 Priority and issue type strings hardcoded all over the place

          • Medium - Medium priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-23200 Issue Types are not sorted alphabitically anymore after renaming any issue type

          • Low - Low priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-23613 priority level names don't update

          • Low - Low priority issues
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-24146 After workflow scheme migration, issue moved to a newly added status are not readable

          • High - High priority issues
          • Closed

          Activity

            People

              pleschev Peter Leschev
              nick.menere Nick Menere [Atlassian] (Inactive)
              Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: