JIra Status Sequence Reset

XMLWordPrintable

    • 3
    • Minor
    • 44
    • Hide

      Customer Update — Status Order Display Issue in Admin View

      We identified the root cause of the issue where the status ordering in Settings → Work Items → Statuses appeared to be reset after Jira Cloud updates.

      What happened:
      A feature gate introduced in a recent release caused the status list in the admin view to display in an incorrect order based on internal sequence IDs, rather than the custom ordering configured by administrators. This was a read view issue only — your underlying status configuration and ordering were not affected.

      What we've done:
      We have disabled the feature gate responsible for this display behavior. The Statuses admin view will now correctly reflect your configured status ordering again.

      What you need to do:
      No action is required. Since this was a display-only issue, your existing status order remains intact.

      Status: We will continue to monitor to confirm the fix is stable before re-enabling the feature gate with the underlying issue resolved.

      We apologise for the confusion and appreciate your patience. If you have any questions or continue to experience issues, please don't hesitate to reach out.

      Show
      Customer Update — Status Order Display Issue in Admin View We identified the root cause of the issue where the status ordering in Settings → Work Items → Statuses appeared to be reset after Jira Cloud updates. What happened: A feature gate introduced in a recent release caused the status list in the admin view to display in an incorrect order based on internal sequence IDs, rather than the custom ordering configured by administrators. This was a read view issue only — your underlying status configuration and ordering were not affected. What we've done: We have disabled the feature gate responsible for this display behavior. The Statuses admin view will now correctly reflect your configured status ordering again. What you need to do: No action is required. Since this was a display-only issue, your existing status order remains intact. Status: We will continue to monitor to confirm the fix is stable before re-enabling the feature gate with the underlying issue resolved. We apologise for the confusion and appreciate your patience. If you have any questions or continue to experience issues, please don't hesitate to reach out.
    • Warranty

      Issue Summary

      After a Jira Cloud release, the manually configured status order in Settings > Work Items > Statuses is reset to a random order based on internal sequence IDs, discarding any custom ordering previously applied by the admin.

      Steps to Reproduce

      NOTE: this occurs after Atlassian Applies updates to the site and cannot be manually triggered

      1. Navigate to Jira Settings > Work Items > Statuses
      1. Manually reorder statuses using the up/down arrows to a preferred order (e.g., alphabetical)
      1. After a Jira Cloud release is applied to the instance that affects Status 
      1. Navigate back to Jira Settings > Work Items > Statuses

      Expected Results

      The custom status order set by the admin is preserved across Jira Cloud releases.

      Actual Results

      The status order is reset to a random sequence following a Jira Cloud release. The previously applied manual ordering is lost with no way to restore it.

      Workaround

      Currently there is no known workaround for this behavior. Manually reordering via the up/down arrows is possible but is not a viable workaround as the order is subject to being reset again by a subsequent release. A workaround will be added here when available.

      NOTE: Manual reconfiguration to return the statuses to the origional configuration is currently Blocked by this Bug and feature:

              Assignee:
              Unassigned
              Reporter:
              Earl McCutcheon
              Votes:
              7 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: