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

          Form Name

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

            Akhil Karun (Inactive) made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 638828 ]
            Sarath Padarthi made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 634271 ]
            Jason Anderson made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 611820 ]

            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!
            Sarah A made changes -
            Summary Original: Issue removed from Sprint not showing in Burndown Chart or Sprint Report. New: Issue removed from Sprint not showing in Burndown Chart or Sprint Report
            Sarah A made changes -
            Description Original: {panel:bgColor=#e7f4fa}
            *NOTE:* This bug report is for *JIRA Software Server*. Using *JIRA Software Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JSWCLOUD-14984].
            {panel}
            h3. Summary
            h3. 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:*
             # Create a JIRA Software Project
             # Create a Sprint - You can start the Sprint or not.
             # Create an issue and set the Sprint in the issue creation screen
             ** Start the Sprint if you have not started.
             # Remove the issue from the Sprint.

            h3. 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:*
             # Create an issue
             # Move the issue to the active sprint
             # Complete the sprint and choose to move the issue to the backlog
             # Create a new Sprint
             # Move the issue to the active sprint (Start the Sprint if its not started)
             # Move the issue back to the backlog
             # The issue will disappear from the burndown chart although it was originally created in the backlog without specifying a sprint

            h3. Expected Results

            The burndown chart would show the issue as "Scope change issue removed"
            h3. Actual Results

            The burndown chart does not show the issue on it and make it seems like the issue never existed.
            h3. 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 effects the output of the velocity chart
            h3. Note

            Affected deleted issue.             		New: {panel:bgColor=#e7f4fa}
            *NOTE:* This bug report is for {*}JIRA Software Server{*}. Using {*}JIRA Software Cloud{*}? [See the corresponding bug report|http://jira.atlassian.com/browse/JSWCLOUD-14984].
            {panel}
            h3. Summary
            h3. 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:*
             # Create a JIRA Software Project
             # Create a Sprint - You can start the Sprint or not.
             # Create an issue and set the Sprint in the issue creation screen
             ** Start the Sprint if you have not started.
             # Remove the issue from the Sprint.

            h3. 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:*
             # Create an issue
             # Move the issue to the active sprint
             # Complete the sprint and choose to move the issue to the backlog
             # Create a new Sprint
             # Move the issue to the active sprint (Start the Sprint if its not started)
             # Move the issue back to the backlog
             # The issue will disappear from the burndown chart although it was originally created in the backlog without specifying a sprint

            h3. Expected Results

            The burndown chart would show the issue as "Scope change issue removed"
            h3. Actual Results

            The burndown chart does not show the issue on it and make it seems like the issue never existed.
            h3. 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
            h3. Note

            Affected deleted issue.
            Sarah A made changes -
            Fix Version/s New: 8.13.15 [ 97900 ]

            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.

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

                Created:
                Updated:
                Resolved: