Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-7232

Unable to complete a sprint if sub-task status is not included in the Done column

XMLWordPrintable

      When Sub-tasks use a separate Workflow, and their final Status ID is different from that of the main tasks, JIRA Agile will not allow the user to complete the Sprint unless the sub-tasks are included in the Board filter. The cause is that it's looking only for Status IDs included in the Done column.

      Steps to reproduce:

      1. create a Sprint on a Board with a filter that doesn't include Sub-tasks;
      2. finish all tasks on the board as well as the sub-tasks;
      3. try to complete the Sprint: Agile will complain about Sub-tasks not being finished.

      Workaround: modify the Board filter so that the Sub-task final status is included in the Done column. Make sure the resolved status for your sub-tasks is placed in the green column.

          Form Name

            [JSWSERVER-7232] Unable to complete a sprint if sub-task status is not included in the Done column

            MEDITECH ADMIN TEAM added a comment -

            If this is still a problem, why hasn't Atlassian re-opened this issue or created a new one?

            MEDITECH ADMIN TEAM added a comment - If this is still a problem, why hasn't Atlassian re-opened this issue or created a new one?

            Jason Kemp added a comment -

            This still frequently comes up within our organization. This is still a bug, or poor design choice. Either way, it needs to be corrected.

            Jason Kemp added a comment - This still frequently comes up within our organization. This is still a bug , or poor design choice. Either way, it needs to be corrected.

            Jason Kemp added a comment -

            This is not fixed in 7.6.3. Why not just use the workflow state's category (To Do / In progress / Done) to determine the done-ness when closing a sprint?

            Jason Kemp added a comment - This is not fixed in 7.6.3. Why not just use the workflow state's category (To Do / In progress / Done) to determine the done-ness when closing a sprint?

            Doug Robinson added a comment -

            We are on v7.3.0.

            not fixed yet.

            Doug Robinson added a comment - We are on v7.3.0. not fixed yet.

            Samip Banker added a comment - - edited

            We just upgraded to 6.7.11 hoping this problem will be fixed by this version... but we still face the same problem.
            "The following issues, which have all their sub-tasks done, will be returned to the backlog as they are not yet complete:"
            Where our board only pulls issues they are requirements and req. don't have "Done" status... but "Sub-Task" do...
            Can someone educate us if 6.7.11 fixed this problem....

            Samip Banker added a comment - - edited We just upgraded to 6.7.11 hoping this problem will be fixed by this version... but we still face the same problem. "The following issues, which have all their sub-tasks done, will be returned to the backlog as they are not yet complete:" Where our board only pulls issues they are requirements and req. don't have "Done" status... but "Sub-Task" do... Can someone educate us if 6.7.11 fixed this problem....

            Gwen Gelsinon added a comment - - edited

            also watching this issue. hope a permanent fix is implemented soon

            getting this message when the issue is resolved, closed and all subtasks are closed:
            "The following issues, which have all their sub-tasks done, will be returned to the backlog as they are not yet complete:"
            Hope it gets attention soon. Thanks!

            Gwen Gelsinon added a comment - - edited also watching this issue. hope a permanent fix is implemented soon getting this message when the issue is resolved, closed and all subtasks are closed: "The following issues, which have all their sub-tasks done, will be returned to the backlog as they are not yet complete:" Hope it gets attention soon. Thanks!

            Mike Seal added a comment -

            Work around has worked but this seems very weak as a solution. sub tasks used to separate out work for development team but also includes sub tasks relating to the Test team.

            Mike Seal added a comment - Work around has worked but this seems very weak as a solution. sub tasks used to separate out work for development team but also includes sub tasks relating to the Test team.

            Simon Kühn added a comment -

            Here too. Complicated issue-workflow, simple sub-issue workflow, but our board should only show the issues. And I wondered why I could not close the sprint. Workaround established but not the solution I guess...

            Simon Kühn added a comment - Here too. Complicated issue-workflow, simple sub-issue workflow, but our board should only show the issues. And I wondered why I could not close the sprint. Workaround established but not the solution I guess...

            Laszlo Kremer added a comment -

            Affects us too. There are open localization sub-tickets when the story ends. These will be done by an other team after the story is finished in the sprint, and has to be under the story to keep track. The localization sub-tasks are filtered out by the board filter, but the complete sprint button ignores that.

            Laszlo Kremer added a comment - Affects us too. There are open localization sub-tickets when the story ends. These will be done by an other team after the story is finished in the sprint, and has to be under the story to keep track. The localization sub-tasks are filtered out by the board filter, but the complete sprint button ignores that.

            Daniel Desjardins added a comment - - edited

            Hello,
            This is actually very problematic for my team because in our company, we have many development teams, each working using SCRUM, but we have only 1 QA/QC team, which work using Kanban.

            QA adds their own subtasks on our main stories/problems issues, but we filter them out as they do not pertain to our sprint. The problem is that when we want to close/release the sprint in Greenhopper it won't let us for any issue which has some subtasks not in the DONE column. As we do not even see those in our sprint (on purpose), we need to deal with QA to temporarily move their sub-tasks to a status that fits in the DONE column.

            Basically, releasing a sprint should only take into considerations the sub-tasks that are seen by the filter.

            Thank you for your help on this!
            (at the time of writing we are using still JIRA 5.2 and GH 6.2.2.2)

            Daniel Desjardins added a comment - - edited Hello, This is actually very problematic for my team because in our company, we have many development teams, each working using SCRUM, but we have only 1 QA/QC team, which work using Kanban. QA adds their own subtasks on our main stories/problems issues, but we filter them out as they do not pertain to our sprint. The problem is that when we want to close/release the sprint in Greenhopper it won't let us for any issue which has some subtasks not in the DONE column. As we do not even see those in our sprint (on purpose), we need to deal with QA to temporarily move their sub-tasks to a status that fits in the DONE column. Basically, releasing a sprint should only take into considerations the sub-tasks that are seen by the filter. Thank you for your help on this! (at the time of writing we are using still JIRA 5.2 and GH 6.2.2.2)

              Unassigned Unassigned
              dwierzbicka Dobroslawa Wierzbicka (Inactive)
              Affected customers:
              19 This affects my team
              Watchers:
              33 Start watching this issue

                Created:
                Updated:
                Resolved: