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

      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

            Bugfix Automation Bot made changes -
            Minimum Version New: 6.03
            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2855738 ] New: JAC Bug Workflow v3 [ 2937879 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2542670 ] New: JAC Bug Workflow v2 [ 2855738 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1549194 ] New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2542670 ]
            jonah (Inactive) made changes -
            Description Original: 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:*
            # Create a new Sprint
            # Create 3 issues and add them to the sprint
            # Move one out
            # Start the Sprint
            # Look at Sprint Report (the removed issue will be there)
            # look at the Burndown report (the Start Sprint event will show only 2 issues, which is correct)


            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-9797].
              {panel}

            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:*
            # Create a new Sprint
            # Create 3 issues and add them to the sprint
            # Move one out
            # Start the Sprint
            # Look at Sprint Report (the removed issue will be there)
            # look at the Burndown report (the Start Sprint event will show only 2 issues, which is correct)


            jonah (Inactive) made changes -
            Link New: This issue relates to JSWCLOUD-9797 [ JSWCLOUD-9797 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels Original: affects-server fixme future_sprints New: affects-cloud affects-server fixme future_sprints
            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 [ 908601 ] New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1549194 ]
            Oswaldo Hernandez (Inactive) made changes -
            Workflow Original: GreenHopper Kanban Workflow 20141014 [ 746857 ] New: JIRA Bug Workflow w Kanban v6 [ 908601 ]

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

                Created:
                Updated:
                Resolved: