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

Issue removed from Sprint not showing in Burndown Chart or Sprint Report when moving from Sprint to Sprint

XMLWordPrintable

      Issue Summary

      Some issues removed from sprints are no showing under the 'Issues Removed From Sprint' section when looking at the Sprint Report, when moving the issue from Sprint to Sprint.

      Steps to Reproduce

      1. Create a Sprint A
      2. Create a Sprint B
      3. Create a Sprint C
      4. Create some issues (Issue 1, Issue 2, Issue 3) and move them to Sprint A
      5. Start Sprint A
      6. Move the Issue 1 from Sprint A to Sprint B
      7. Complete Sprint A - incomplete issues go to backlog
      8. Check the 'Issue Removed From Sprint' section in the Sprint Report (Issue 1 should correctly show as removed from Sprint A) ** 
      9. Move Issue 2 and Issue 3 to Sprint B
      10. Start Sprint B
      11. Move again the Issue 1 to Sprint C
      12. Complete Sprint B
      13. Check the 'Issue Removed From Sprint' section in the Sprint Report from Sprint B, we will see that Issue 1 will be missing.

       Sample video: 

      Issue Removed from Sprint bug.mov

      Expected Results

      Issue 1 is listed in the 'Issue Removed From Sprint' section in the Sprint Report from Sprint B

      Actual Results

      Issue 1 is not listed in the 'Issue Removed From Sprint' section in the Sprint Report from Sprint B

      Workaround

      Currently, there is no known workaround for this behavior. A workaround will be added here when available

        1. image-2021-01-19-12-32-39-967.png
          image-2021-01-19-12-32-39-967.png
          45 kB
        2. image-2021-01-19-12-36-38-379.png
          image-2021-01-19-12-36-38-379.png
          62 kB
        3. Issue Removed from Sprint bug.mov
          30.18 MB

            [JSWSERVER-20815] Issue removed from Sprint not showing in Burndown Chart or Sprint Report when moving from Sprint to Sprint

            Yana Stoliarova added a comment -

            8.13.13 is affected and it is critical for us to have the bug fixed in this version as well

            Yana Stoliarova added a comment - 8.13.13 is affected and it is critical for us to have the bug fixed in this version as well

            Johna.S.Lee added a comment -

            For Jira users, if you have confirmed the fix is good, pls comment here

            Johna.S.Lee added a comment - For Jira users, if you have confirmed the fix is good, pls comment here

            Jill Goodwin added a comment -

            8.13.4 is impacted from this as well

            Jill Goodwin added a comment - 8.13.4 is impacted from this as well

            Andrew Frayling added a comment -

            8.14.1 is also affected. And from what I've observed an issue doesn't even have to be moved multiple times, just moving from Sprint A to Sprint B is enough for an issue to not be included in the Sprint Report and Burndown Chart for Sprint A.

            Andrew Frayling added a comment - 8.14.1 is also affected. And from what I've observed an issue doesn't even have to be moved multiple times, just moving from Sprint A to Sprint B is enough for an issue to not be included in the Sprint Report and Burndown Chart for Sprint A.

            Christon Khong added a comment -

            8.13.2 is affected

            Christon Khong added a comment - 8.13.2 is affected

            Mykola Vysochyn added a comment -

            8.13.9 is also affected.

            Mykola Vysochyn added a comment - 8.13.9 is also affected.

            Azfar Masut added a comment -

            the reports are really crucial for us, is there any workaround for this?

            Azfar Masut added a comment - the reports are really crucial for us, is there any workaround for this?

            Yogesh Kumar added a comment -

            This is impacting our Report accuracy.

            We are using 8.5.7.

            Each of the 3 processes (gadget/report/dashboard) creates unique outputs.   Reports and portal use the Jira DB as input (the only source available), and the gadget uses both the Jira DB .. AND a proprietary scan of the transaction logs to capture, parse, and build different results set.  There is no logical method by which you can use any of the 3 consumers of Jira data (gadget/reports/portal) to compare with any of the 3 results sets that would allow you to land on the same results set. inaccurate reporting is extremely frustrating. Please prioritize this ticket.

            Yogesh Kumar added a comment - This is impacting our Report accuracy. We are using 8.5.7. Each of the 3 processes (gadget/report/dashboard) creates unique outputs.   Reports and portal use the Jira DB as input (the only source available), and the gadget uses both the Jira DB .. AND a proprietary scan of the transaction logs to capture, parse, and build different results set.  There is no logical method by which you can use any of the 3 consumers of Jira data (gadget/reports/portal) to compare with any of the 3 results sets that would allow you to land on the same results set.  inaccurate reporting  is extremely frustrating. Please prioritize this ticket.

            Binaya Kc added a comment -

            This is affecting all users in our instance. 

            We are on v8.15.1. 
            Please prioritize this ticket. Our reports are all messed up and there is no way of knowing about the scope change at all.

            Binaya Kc added a comment - This is affecting all users in our instance.  We are on v8.15.1.  Please prioritize this ticket. Our reports are all messed up and there is no way of knowing about the scope change at all.

            Iwona Zydek added a comment - - edited

            Could anyone tell us when we can expect to have it fixed please? 
            I've been struggling with this error for about 2 months and it is very disturbing, as it is one of basic functions for SMs to track the scope changes and capacity in the sprint.

            Iwona Zydek added a comment - - edited Could anyone tell us when we can expect to have it fixed please?  I've been struggling with this error for about 2 months and it is very disturbing, as it is one of basic functions for SMs to track the scope changes and capacity in the sprint.

              15c9fc99333a Maciej Sujkowski (Inactive)
              7d74d3b1a350 Rodrigo Jose Zaparoli
              Affected customers:
              54 This affects my team
              Watchers:
              76 Start watching this issue

                Created:
                Updated:
                Resolved: