Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-90402

Removing a status from a workflow makes the issue history and agile reporting inconsistent

XMLWordPrintable

      Issue Summary

      It appears Jira Software loses visibility on an issue's change history when a previously existing status is removed ( changed ) from the project's workflow. This affects the historical reporting on the various agile charts for the affected project.

      Steps to Reproduce

      1. Configure a workflow with some statuses, for example
        1. Open -> In Progress -> Resolved -> Closed
      2. Create a sprint, add an issue from the backlog, transition every step from Open until Closed, and complete the sprint
      3. Create new workflow with another set of statuses
        1. Open -> In Progress -> Status 9
      4. Migrate workflow, map issues in Resolved and Closed to Status 9

      Expected Results

      Agile reports are unaffected by this change

      Actual Results

      Sprint report show issues moved from Resolved and Closed to Status 9 as being In Progress and Removed From Sprint. Cycle Time is also incorrectly calculated for these issues as well. See attached screenshots.

      Issue history shows the move between statuses

      Sprint report shows issues as removed from sprint.instead

      Workaround

      Modify the affect project's workflow, add changed status back, and map this status to a column in the project's agile board(respective to their position in the old board i.e. far right or far left) They do not need transitions to or from other statuses. In the example above Agile reporting is fixed by adding Resolved and Closed back to the affected project's workflow and mapping the statuses to the Done column accordingly. See attached screenshot.

        1. image-2023-09-07-11-25-09-953.png
          image-2023-09-07-11-25-09-953.png
          130 kB
        2. image-2023-09-07-11-55-08-982.png
          image-2023-09-07-11-55-08-982.png
          139 kB
        3. image-2023-09-07-12-42-58-332.png
          image-2023-09-07-12-42-58-332.png
          139 kB
        4. image-2023-09-07-12-43-13-656.png
          image-2023-09-07-12-43-13-656.png
          139 kB
        5. image-2023-09-07-12-43-28-044.png
          image-2023-09-07-12-43-28-044.png
          130 kB

            [JRACLOUD-90402] Removing a status from a workflow makes the issue history and agile reporting inconsistent

            Akhil Karun (Inactive) added a comment -

            Hello d80b1397fd0f the behaviour is due to the fact that Jira considers right most status to be 'Done' and reports always presenting real-time data. AFAIK, it was a design decision at the time of architecting jira/reports. To change this behaviour, please vote for this as feature request here:
            https://jira.atlassian.com/browse/JSWCLOUD-15106

            Akhil Karun (Inactive) added a comment - Hello d80b1397fd0f the behaviour is due to the fact that Jira considers right most status to be 'Done' and reports always presenting real-time data. AFAIK, it was a design decision at the time of architecting jira/reports. To change this behaviour, please vote for this as feature request here: https://jira.atlassian.com/browse/JSWCLOUD-15106

            Akhil Karun (Inactive) added a comment -

            Hi all,

            Thanks for letting us know about this issue. We are closing this bug because it can no longer be reproduced from the outlined steps. Feel free to re-open if you are able reproduce the problem and mention the exact steps to reproduce it. 
            Note: The old 'done' statuses needs be in the unmapped status column at least for the reports to work whenever.

            Thanks,

            Akhil

            Akhil Karun (Inactive) added a comment - Hi all, Thanks for letting us know about this issue. We are closing this bug because it can no longer be reproduced from the outlined steps. Feel free to re-open if you are able reproduce the problem and mention the exact steps to reproduce it.  Note: The old 'done' statuses needs be in the unmapped status column at least for the reports to work whenever. Thanks, Akhil

              Unassigned Unassigned
              3638101d8c0a Jose Gochi
              Affected customers:
              5 This affects my team
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: