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

Issue removed from Sprint not showing in Burndown Chart or Sprint Report

XMLWordPrintable

    • 7.01
    • 48
    • Severity 2 - Major
    • 694
    • Hide
      Atlassian Update – 23 Jun 2020

      Hi All,

      The problem will automatically be fixed in Jira 8.11 for all the newly created and edited issues and they will display in the Sprint Report and Burndown Chart.
      If you are not concerned about the past issues, you don’t have to take any action. However, if you want to be sure all the past issues get fixed too, you need to perform a full reindex.

      We will continue to watch this issue for further updates, so feel free to share your thoughts in the comments.

      Thank you,
      Your Jira Server Bug Fix team

      Show
      Atlassian Update – 23 Jun 2020 Hi All, The problem will automatically be fixed in Jira 8.11 for all the newly created and edited issues and they will display in the Sprint Report and Burndown Chart. If you are not concerned about the past issues, you don’t have to take any action. However, if you want to be sure all the past issues get fixed too, you need to perform a full reindex. We will continue to watch this issue for further updates, so feel free to share your thoughts in the comments. Thank you, Your Jira Server Bug Fix team

      NOTE: This bug report is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding bug report.

      Summary

      Scenario A

      Issues which Sprint has been set at creation issue screen will not appear in burndown chart if the sprint is removed from this issue.
      Steps to Reproduce:

      1. Create a JIRA Software Project
      2. Create a Sprint - You can start the Sprint or not.
      3. Create an issue and set the Sprint in the issue creation screen
        • Start the Sprint if you have not started.
      4. Remove the issue from the Sprint.

      Scenario B

      The is also applicable for issues in the backlog that were previously associated with an active sprint and moved back to the backlog when the sprint is completed.
      Steps to reproduce:

      1. Create an issue
      2. Move the issue to the active sprint
      3. Complete the sprint and choose to move the issue to the backlog
      4. Create a new Sprint
      5. Move the issue to the active sprint (Start the Sprint if its not started)
      6. Move the issue back to the backlog
      7. The issue will disappear from the burndown chart although it was originally created in the backlog without specifying a sprint

      Expected Results

      The burndown chart would show the issue as "Scope change issue removed"

      Actual Results

      The burndown chart does not show the issue on it and make it seems like the issue never existed.

      Workaround

      The only known workaround for now is to put the issue back in the Sprint after removal and then remove again
      No known workaround at this time, the previously noted workaround affects the output of the velocity chart

      Note

      Affected deleted issue.

        1. The chart you need to monitor your sprint.msg
          97 kB

            [JSWSERVER-14984] Issue removed from Sprint not showing in Burndown Chart or Sprint Report

            German Gold added a comment -

            The bug is on version  v8.13.8 as well, so frustrating!

            German Gold added a comment - The bug is on version  v8.13.8 as well, so frustrating!

            artyom.dalibaltyan added a comment -

            The issue is reproducible on 8.16.1 version as well. Can we get an assist for this to get the reports reflected correctly?

            artyom.dalibaltyan added a comment - The issue is reproducible on 8.16.1 version as well. Can we get an assist for this to get the reports reflected correctly?

            Sreedevi Raman Pisharody added a comment -

            We are running on 8.13.9 and our project teams seems to be affected by this issue. Please provide us with a workaround so that the metrics reported in the reports are correctly reflected.

            Sreedevi Raman Pisharody added a comment - We are running on 8.13.9 and our project teams seems to be affected by this issue. Please provide us with a workaround so that the metrics reported in the reports are correctly reflected.

            Farhan Ahmed added a comment -

            8.13.9 is impacted as well. We had a project team complain about this again this week.

            Farhan Ahmed added a comment - 8.13.9 is impacted as well. We had a project team complain about this again this week.

            Sid added a comment -

            Quick update:
            We are on JIRA DC v8.15.1 and were seeing this issue, getting complaints from our users every day.

            Last week, for some reason, our index got corrupted and we had to rebuild our index from scratch.
            Once that was done this issue magically got resolved.
            Might not be applicable to every version but might be worth a try

            Sid added a comment - Quick update: We are on JIRA DC v8.15.1 and were seeing this issue, getting complaints from our users every day. Last week, for some reason, our index got corrupted and we had to rebuild our index from scratch. Once that was done this issue magically got resolved. Might not be applicable to every version but might be worth a try

            Jordan Wilkinson added a comment -

            Seeing the problem on 8.13.6 and 8.13.2. Please reopen this issue.

            Jordan Wilkinson added a comment - Seeing the problem on 8.13.6 and 8.13.2. Please reopen this issue.

            Omid H. added a comment -

            8.13.6 is affected

            Omid H. added a comment - 8.13.6 is affected

            Fides Aarts added a comment - - edited

            We are facing this issue with version Jira v8.18.1. So it is not fixed as indicated. Our sprint results are useless due to this bug. Why is it so difficult to fix this bug?

            Fides Aarts added a comment - - edited We are facing this issue with version Jira v8.18.1. So it is not fixed as indicated. Our sprint results are useless due to this bug. Why is it so difficult to fix this bug?

            petrvokoun added a comment -

            I just stopped watching this issue, its useless. 

            Really american approach - never admit anything is wrong and let users use Jira where a crucial function does not work  Im glad we moved from on-premise solution to another non-Atlassian solution.

            Goodbye. And good luck to everyone else.

            petrvokoun added a comment - I just stopped watching this issue, its useless.  Really american approach - never admit anything is wrong and let users use Jira where a crucial function does not work  Im glad we moved from on-premise solution to another non-Atlassian solution. Goodbye. And good luck to everyone else.

            Mark.Bonifay added a comment -

            Users in our instance running 8.13.10 are still reporting this problem as well. 

            Mark.Bonifay added a comment - Users in our instance running 8.13.10 are still reporting this problem as well. 

              twieckowski Tomasz Wieckowski (Inactive)
              aborzzatto Andre Borzzatto
              Affected customers:
              246 This affects my team
              Watchers:
              226 Start watching this issue

                Created:
                Updated:
                Resolved: