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

Unable to close Sprint with closed parent issue and open sub-tasks

XMLWordPrintable

    • 2
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Problem Definition

      It is possible to close a parent issue (set to done) with open sub-tasks. When a user attempts to close a Sprint with these issues, a generic error occurs:

      Sprint cannot be completed as there are incomplete subtasks on the following issues:

      Suggested Solution

      If there is a closed parent issue with open sub-tasks, it should give the user the option to either move all sub-tasks to done, or re-open the parent issue.

      Workaround

      Re-open the parent issue or close the sub-tasks using Bulk Change operations

        1. sprint_closure2.jpg
          sprint_closure2.jpg
          92 kB
        2. Screenshot 2017-03-23 16.08.48.png
          Screenshot 2017-03-23 16.08.48.png
          362 kB

            [JSWSERVER-12012] Unable to close Sprint with closed parent issue and open sub-tasks

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3069890 ] New: JAC Suggestion Workflow 3 [ 3662683 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2622208 ] New: JAC Suggestion Workflow [ 3069890 ]
            Gosia Kowalska made changes -
            Resolution New: Won't Do [ 10000 ]
            Status Original: Gathering Interest [ 11772 ] New: Resolved [ 5 ]

            Gosia Kowalska added a comment -
            Atlassian Update – 27 March 2018

            Hi,

            Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance.

            For more context, check out our Community blog on our renewed approach to highly voted Server suggestions for Jira and Confluence.

            Thanks again.
            Regards,
            Jira Product Management

            Gosia Kowalska added a comment - Atlassian Update – 27 March 2018 Hi, Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance. For more context, check out our Community blog on our renewed approach to highly voted Server suggestions for Jira and Confluence . Thanks again. Regards, Jira Product Management
            SET Analytics Bot made changes -
            Support reference count New: 2
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2320913 ] New: Confluence Workflow - Public Facing v4 [ 2622208 ]
            Status Original: Open [ 1 ] New: Gathering Interest [ 11772 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 2040180 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2320913 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2028739 ] New: JIRA PM Feature Request Workflow v2 [ 2040180 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 857315 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2028739 ]
            K. Yamamoto made changes -
            Comment [ A comment with security level 'atlassian-staff' was removed. ]

              Unassigned Unassigned
              smackie@atlassian.com Shannon S
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: