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

Issues which are added to a future sprint and resolved before the sprint is started still appear in the sprint

XMLWordPrintable

      The symptom here is if you add an issue to a future sprint, then resolve it, then start the sprint, the issue appears in the sprint on Work Mode and Sprint Report/Burndown Chart.

      There is a mild inconsistency with the reporting of the estimate value between Sprint Report and Burndown Chart. The Burndown Chart shows the issue coming into the sprint with a value of 0, regardless of the actual estimate. This is because the issue was already 'burnt down' before the sprint started. The Sprint Report on the other hand, shows the value of the estimate when the sprint started, which may be non-zero.

      Therefore the fix here may be around making the reporting more consistent/accurate, or it may be around not bringing such issues into the sprint in the first place. The latter could be difficult to solve due to issues potentially appearing on multiple boards.

            [JSWSERVER-9854] Issues which are added to a future sprint and resolved before the sprint is started still appear in the sprint

            Bugfix Automation Bot made changes -
            Minimum Version New: 6.03
            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2853356 ] New: JAC Bug Workflow v3 [ 2934468 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2546033 ] New: JAC Bug Workflow v2 [ 2853356 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1552081 ] New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2546033 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels Original: fixme future_sprints New: affects-server fixme future_sprints
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 909805 ] New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1552081 ]

            Mihai Nitu added a comment -

            Hello,

            The Fix Version for this issue is 6.6.51.
            We are using JIRA Agile 6.6.80 and it looks like this issue is still reproducible.
            Steps to reproduce it:
            1. Create an issue.
            2. Add it to a sprint that is not started yet.
            3. Resolve the issue.
            4. Start the sprint.

            Even if resolved/closed issues are not supposed to be displayed in "Backlog" mode ("Plan mode" in older versions), it will be present in the under the respective sprint. Removing it from the sprint will also affect the consistency of the reporting, as specified in the original description.

            Best Regards,
            Mihai

            Mihai Nitu added a comment - Hello, The Fix Version for this issue is 6.6.51. We are using JIRA Agile 6.6.80 and it looks like this issue is still reproducible. Steps to reproduce it: 1. Create an issue. 2. Add it to a sprint that is not started yet. 3. Resolve the issue. 4. Start the sprint. Even if resolved/closed issues are not supposed to be displayed in "Backlog" mode ("Plan mode" in older versions), it will be present in the under the respective sprint. Removing it from the sprint will also affect the consistency of the reporting, as specified in the original description. Best Regards, Mihai
            Mohamed Riza (Inactive) made changes -
            Link New: This issue relates to GHS-12785 [ GHS-12785 ]
            Oswaldo Hernandez (Inactive) made changes -
            Workflow Original: GreenHopper Kanban Workflow 20141014 [ 747538 ] New: JIRA Bug Workflow w Kanban v6 [ 909805 ]
            Martin (Inactive) made changes -
            Fix Version/s New: 6.6.51 [ 50500 ]
            Resolution New: Fixed [ 1 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]

              Unassigned Unassigned
              mtokar Michael Tokar
              Affected customers:
              8 This affects my team
              Watchers:
              17 Start watching this issue

                Created:
                Updated:
                Resolved: