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

Issue moved out of sprint before start, still shows on reports

XMLWordPrintable

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

      When an issue is moved out of a Sprint before starting it (moved to Backlog or another Sprint) when the Sprint is Started, removed issue will still appear on Sprint Report.

      Steps to reproduce:

      1. Create a new Sprint
      2. Create 3 issues and add them to the sprint
      3. Move one out
      4. Start the Sprint
      5. Look at Sprint Report (the removed issue will be there)
      6. look at the Burndown report (the Start Sprint event will show only 2 issues, which is correct)

        1. SprintStart1.jpeg
          SprintStart1.jpeg
          131 kB
        2. SprintStart2.jpeg
          SprintStart2.jpeg
          96 kB
        3. SprintStart3.jpeg
          SprintStart3.jpeg
          93 kB
        4. SprintStart4.jpeg
          SprintStart4.jpeg
          58 kB
        5. SprintStart5.jpeg
          SprintStart5.jpeg
          119 kB

            [JSWSERVER-9797] Issue moved out of sprint before start, still shows on reports

            erento GmbH added a comment -

            Hi there, i can confirm the problem is now fixed! Thanks.

            erento GmbH added a comment - Hi there, i can confirm the problem is now fixed! Thanks.

            Michael Tokar added a comment -

            The new version has been deployed to OnDemand.

            If this has not fixed your particular problem, please file a support ticket at support.atlassian.com.

            Michael Tokar added a comment - The new version has been deployed to OnDemand. If this has not fixed your particular problem, please file a support ticket at support.atlassian.com .

            Michael Tokar added a comment -

            The new version of JIRA Agile, which contains the fix, will be made available to OnDemand customers as soon as possible. This will likely occur within the next few days. I'll post a comment here when it goes live.

            Michael Tokar added a comment - The new version of JIRA Agile, which contains the fix, will be made available to OnDemand customers as soon as possible. This will likely occur within the next few days. I'll post a comment here when it goes live.

            Matthew Manger added a comment -

            I am using the On-Demand version and the sprint report and velocity report are still not working correctly.

            Matthew Manger added a comment - I am using the On-Demand version and the sprint report and velocity report are still not working correctly.

            Sujith Gokuladas added a comment -

            This issue should be sufficient for that as well since it is about the "reports" in general. However, I have just created a clone of this issue specifically for Velocity Charts. https://jira.atlassian.com/browse/GHS-9919

            Sujith Gokuladas added a comment - This issue should be sufficient for that as well since it is about the "reports" in general. However, I have just created a clone of this issue specifically for Velocity Charts. https://jira.atlassian.com/browse/GHS-9919

            Doran Sheftall added a comment -

            Has the Velocity Chart issue been re-reported? If so, do you have the Jira ID?

            Doran Sheftall added a comment - Has the Velocity Chart issue been re-reported? If so, do you have the Jira ID?

            Sujith Gokuladas added a comment -

            This issue with the Sprint Reports has been fixed in the on demand instance as well. However, the Velocity Charts are still showing wrong data

            Sujith Gokuladas added a comment - This issue with the Sprint Reports has been fixed in the on demand instance as well. However, the Velocity Charts are still showing wrong data

            Doran Sheftall added a comment -

            Hi all, Jira OnDemand follows a different version number path. Can anyone confirm this is fixed for OnDemand?

            Doran Sheftall added a comment - Hi all, Jira OnDemand follows a different version number path. Can anyone confirm this is fixed for OnDemand?

            Karl Catling added a comment -

            Just confirming that the fix has worked for us too.

            Karl Catling added a comment - Just confirming that the fix has worked for us too.

            Tyler Bannister added a comment - - edited

            This morning we upgraded to JIRA 6.3.2.2 and after the restart the affected sprint report is now showing the correct information.

            Tyler Bannister added a comment - - edited This morning we upgraded to JIRA 6.3.2.2 and after the restart the affected sprint report is now showing the correct information.

              Unassigned Unassigned
              mfernandezbadii Mauro Badii (Inactive)
              Affected customers:
              39 This affects my team
              Watchers:
              53 Start watching this issue

                Created:
                Updated:
                Resolved: