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

Update Report Logic where 'Done' is based on a status category or workflow

    • 28
    • 39
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Problem Definition

      Some reports (Velocity Chart, Sprint / Burndown Report) will show completed issues as not done or completed outside the sprint if the workflow is changed, where by the DONE status is unmapped from the board and not mapped to the last (right most) column on the board.

      Jira business logic defines issues that are in the last column as complete. Any issues that aren’t in the last column on the board will be considered incomplete, irrespective of the status category mapped to that column.

      This impacts the data that’s pulled through to reports.

      Suggested Solution

      Update Jira business / report logic where ‘Done’ is based on a status category or workflow and not column position.

      Why this is important

      Users with workflows that do not have ‘Done’ or ‘Done’ mapped to the last column will not be able to use reports for insights.

      Atlassian Status Update - 22nd March 2021

      Hi everyone,

      Thanks for your feedback on this problem. We appreciate the time that you took to help us be better.

      Though not ideal in some cases, the behaviour in-product today is not a bug. Proposed improvements here are a feature request and have to be prioritized against other requests.

      This is how reports and boards work in Jira:

      1. Reports and sprints are burning down issues based on the last column on the board.
      2. Our current reports are not built to report issues being done based on an issue’s entire lifecycle (done-done), but based on when each board’s work is done (last column), and the reports belong only to one board.

      Expected Result
      As a user, I update my board’s workflow. I don’t map the Done status to the last column on the board. What this means is:

      • The Done status category is no longer associated with the last column on the board.
      • The column with the Done status category is now in another position on the board (that’s not the last column).
      • When using multiple boards, some boards intentionally don’t have Done in the last column. One board could be a QA board and the issue is only considered complete when it reaches the Releases board.

      I expect the story points completed in the sprint will show as completed in reports.

      Actual Result
      The business logic in Jira defines issues that are in the last column as complete. Any issues that aren’t in the last column on the board will be considered incomplete, irrespective of the status category mapped to that column.

      This impacts the data that’s pulled through to your reports.

      • The velocity report will show 0 completed story points.
      • The sprint report will convert previously completed issues with a Done status to their previous state such as To do or In progress.

      To mitigate any problems, try this workaround:

      1. Go to Board > Manage workflow.
      2. Add the removed Done status to your workflow. Give the status the same name as previously used in your workflow and reports.
      3. At this stage, avoid adding any incoming transitions.
      4. Save and publish the workflow.
      5. From your board, navigate to the More actions (•••) > Board settings.
      6. In Columns and statuses, move the Done status to the rightmost column.
      7. Hit save.
      8. Your reports should behave as before. Add any incoming transitions to the status.

      We’re using bugs to track any issues that prevent our features from being used as intended.

      But we also understand and appreciate this escalation, and have converted this to a feature suggestion instead. This feature request will allow you to specify which status category is considered done on a board and in existing reports.

      Please watch this Jira issue for future updates as we continue to work on improving reports.

      This feature request requires a large investment and will be prioritized against other high-priority feature requests. On behalf of the Atlassian team, we take your feedback seriously and understand both the frustration and the urgency.

      Please let me know if you have any further questions about this ticket.

      Regards,
      Ivan Teong
      Product Manager, Jira Software Cloud

        1. old done.png
          old done.png
          162 kB
        2. sprint.png
          sprint.png
          134 kB
        3. velocity.png
          velocity.png
          84 kB

            [JRACLOUD-90410] Update Report Logic where 'Done' is based on a status category or workflow

            This is definitely still an enhancement need! We need multiple states of done for tracking completed dev without skewing the metrics on Sprint Completion.

            Suzanne Williams added a comment - This is definitely still an enhancement need! We need multiple states of done for tracking completed dev without skewing the metrics on Sprint Completion.

            Ivan Teong (Inactive) added a comment - - edited

            After detailed investigation into this problem, we discovered that though not ideal in some cases, the behaviour in-product today is not a bug.

            Proposed improvements here are a feature request and have to be prioritized against other requests, as the reports are based on the board's existing logic around the definition of done.

            I've added a status update on our diagnosis into the description of this issue.

            Ivan Teong (Inactive) added a comment - - edited After detailed investigation into this problem, we discovered that though not ideal in some cases, the behaviour in-product today is not a bug. Proposed improvements here are a feature request and have to be prioritized against other requests, as the reports are based on the board's existing logic around the definition of done. I've added a status update on our diagnosis into the description of this issue.

            Abby Kaske added a comment -

            I also cannot put the old status back, like Helen, so the proposed work around is not a solution for me.

            Abby Kaske added a comment - I also cannot put the old status back, like Helen, so the proposed work around is not a solution for me.

            Helen added a comment -

            Goerge, I am in the situation where I can't put the old one back in. (long story). So I am still living in the pain. 

            Helen added a comment - Goerge, I am in the situation where I can't put the old one back in. (long story). So I am still living in the pain. 

            George V added a comment -

            Hellen just add the legacy closed state in your workflow (just floating there) and everything should come back ... 

            it is very annoying issue when it hits you !! we lost lots of useful info

            George V added a comment - Hellen just add the legacy closed state in your workflow (just floating there) and everything should come back ...  it is very annoying issue when it hits you !! we lost lots of useful info

            Helen added a comment - - edited

            when will this get fixed? our sprint report (Sprint 13) got messed up as well... need estimated date on this fix soon... 

            Helen added a comment - - edited when will this get fixed? our sprint report (Sprint 13) got messed up as well... need estimated date on this fix soon... 

            George V added a comment -

            We got impacted by this issue when we transitioned a mature project onto a new workflow.

            We've messed up the sprints by opening & closing them to fix the issue.

            Definately a major one. 

            George V added a comment - We got impacted by this issue when we transitioned a mature project onto a new workflow. We've messed up the sprints by opening & closing them to fix the issue. Definately a major one. 

            This must be fixed ASAP, as the workaround with leaving the old Status in the Workflow is a mess.
            It must be an easy fix for Atlassian to do this

            Br Jakob

             

            Jakob Gormsen added a comment - This must be fixed ASAP, as the workaround with leaving the old Status in the Workflow is a mess. It must be an easy fix for Atlassian to do this Br Jakob  

            This issue can be split into two parts:

            • Velocity Chart - charts are working based on current board configuration. If the current board configuration does not include the "Done" state in the "Done" column, issues in that status are not considered completed. This is why the Velocity Chart is showing zero as the amount of completed work. This wotks as intended.
            • Sprint Report - when it comes to completed issues, the situation is identical as with the Velocity Chart. If an issue is not in a status that is currently mapped to the "Done" column, it will not be considered as completed. However, when a status that the issue is in is not mapped to any column on the board, its status is shown as "To Do", which is incorrect. This will be corrected as part of this ticket.

            Kind regards,
            The JIRA Software Team

            Marek Broda (Inactive) added a comment - This issue can be split into two parts: Velocity Chart - charts are working based on current board configuration. If the current board configuration does not include the "Done" state in the "Done" column, issues in that status are not considered completed. This is why the Velocity Chart is showing zero as the amount of completed work. This wotks as intended. Sprint Report - when it comes to completed issues, the situation is identical as with the Velocity Chart. If an issue is not in a status that is currently mapped to the "Done" column, it will not be considered as completed. However, when a status that the issue is in is not mapped to any column on the board, its status is shown as "To Do", which is incorrect. This will be corrected as part of this ticket. Kind regards, The JIRA Software Team

              Unassigned Unassigned
              rsaputra Adven
              Votes:
              42 Vote for this issue
              Watchers:
              54 Start watching this issue

                Created:
                Updated: