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

Update Sprint Logic where 'Done' is based on a status category

    • 37
    • 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 Statement:

      Team-managed projects consider issues as not done or completed if the DONE status is not mapped to the last (rightmost) column on the board even though there are other columns with the status "Done". Refer to The issues that are Done still shown as "Incomplete when trying to close the Sprint for more details.

       

      Suggested Solution:

      Would be nice if the ‘Done’ is based on a status category and not column position when having multiple columns with Done status.

      Why this is important

      As it's now possible to have multiple done status (JSWCLOUD-17497) on team-managed projects, adding one more column as Done doesn't actually consider it as complete.

      Workaround

      None. Consider adding yourself as a watcher to be kept informed as to the state of this feature request moving forward. With that way, if our development team updates the ticket, you'll be notified via email.

            [JRACLOUD-85722] Update Sprint Logic where 'Done' is based on a status category

            Atlassian Update - November 2023

            After some analysis, we've found that this ticket is a duplicate of the request JSWCLOUD-17670 – Closing Sprints and use of the 'Done column' which has more votes.

            We encourage you to watch and vote on the above instead. All internal ticket references on this ticket have been transferred. If you do not think this issue should have been closed, please add a comment here saying why and we can reopen it.

            Anusha Rutnam added a comment - Atlassian Update - November 2023 After some analysis, we've found that this ticket is a duplicate of the request JSWCLOUD-17670 – Closing Sprints and use of the 'Done column' which has more votes. We encourage you to watch and vote on the above instead. All internal ticket references on this ticket have been transferred. If you do not think this issue should have been closed, please add a comment here saying why and we can reopen it.

            I believe this issue is a duplicate of JSWCLOUD-17670 – Closing Sprints and use of the 'Done column' which has more votes.

            I recommend that watchers of this issue vote on and watch the above issue. So that votes aren't split, I believe this ticket should be closed, but I will wait a week before taking any action in case anyone disagrees. Thank you!

            Anusha Rutnam added a comment - I believe this issue is a duplicate of JSWCLOUD-17670 – Closing Sprints and use of the 'Done column' which has more votes. I recommend that watchers of this issue vote on and watch the above issue. So that votes aren't split, I believe this ticket should be closed, but I will wait a week before taking any action in case anyone disagrees. Thank you!

            Hi my name is Stefan Höltker,
            i work with scrum-but in different teams.

            We implemented a final stage for the review a "reviewd" status, wich is also a "finished" status-type and the right-most status on our board.

             

            The problem now is, that the burndown / up chart wich is a needed tool for us is not working propperly since the "right-most status" is used for it.

             

            Our teams would be more than happy if this can change.

            Stefan Höltker added a comment - Hi my name is Stefan Höltker, i work with scrum-but in different teams. We implemented a final stage for the review a "reviewd" status, wich is also a "finished" status-type and the right-most status on our board.   The problem now is, that the burndown / up chart wich is a needed tool for us is not working propperly since the "right-most status" is used for it.   Our teams would be more than happy if this can change.

            Tony Lenz added a comment -

            Just to tack a little more context on: https://community.atlassian.com/t5/Jira-Software-questions/Next-gen-sprint-project-What-makes-an-issue-complete/qaq-p/1570960?utm_source=atlcomm&utm_medium=email&utm_campaign=immediate_general_reply&utm_content=topic#U1690588

            The assumption of the right most column indicated as "completed" is a decent assumption, but it totally ignores the status of the issue. e.g. if "TO DO" was the most right column all work not started would be considered "completed" during the sprint.

            Tony Lenz added a comment - Just to tack a little more context on: https://community.atlassian.com/t5/Jira-Software-questions/Next-gen-sprint-project-What-makes-an-issue-complete/qaq-p/1570960?utm_source=atlcomm&utm_medium=email&utm_campaign=immediate_general_reply&utm_content=topic#U1690588 The assumption of the right most column indicated as "completed" is a decent assumption, but it totally ignores the status of the issue. e.g. if "TO DO" was the most right column all work not started would be considered "completed" during the sprint.

              Unassigned Unassigned
              65e09325370f Renato Pereira (Inactive)
              Votes:
              28 Vote for this issue
              Watchers:
              31 Start watching this issue

                Created:
                Updated:
                Resolved: