• Type: Bug
• Resolution: Duplicate
• Priority: High (View bug fix roadmap)
• Fix Version/s: None
• Affects Version/s: 6.3.0.2
• Component/s: None
• Labels:

  • affects-cloud
  • affects-server
  • fixme
  • future_sprints
  • todo

[JSWSERVER-8029] Sprint Report shows issues that were removed from the sprint in the "Issues Not Completed" section

Bugfix Automation Bot made changes - 27/Mar/2019 11:24 PM

Minimum Version

New: 6.03

Owen made changes - 16/Oct/2018 1:05 AM

Workflow	Original: JAC Bug Workflow v2 [ 2850741 ]	New: JAC Bug Workflow v3 [ 2933814 ]
Status	Original: Resolved [ 5 ]	New: Closed [ 6 ]

Owen made changes - 25/Sep/2018 12:47 AM

Workflow

Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2545401 ]

New: JAC Bug Workflow v2 [ 2850741 ]

Ignat (Inactive) made changes - 01/Feb/2018 12:08 PM

Workflow

Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1550691 ]

New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2545401 ]

jonah (Inactive) made changes - 02/Apr/2017 11:59 AM

Description

Original: When a sprint is started with a delay (set with a time in the future), issues that are removed from it before it starts in fact are shown as "Issues not Completed" on the Sprint Report. The expected behavior would be to have them show up in the "Removed from Sprint" section, or don't show up at all. Steps to reproduce: # Create a new sprint from a board, add some issues to it. # Start that sprint with a delay. For instance, set start date for the next day. # Remove a few issues from it. # Check Sprint report, you can still see the issues removed from it in the "Issues Not Completed" section. One would expect them to disappear from the report, or at least show in the "Issues Removed from Sprint" section. On the other hand, Burndown Chart will only start burning data when the sprint starts in fact (the next day). # End the sprint. Issues are still shown there regardless.

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-8029].   {panel} When a sprint is started with a delay (set with a time in the future), issues that are removed from it before it starts in fact are shown as "Issues not Completed" on the Sprint Report. The expected behavior would be to have them show up in the "Removed from Sprint" section, or don't show up at all. Steps to reproduce: # Create a new sprint from a board, add some issues to it. # Start that sprint with a delay. For instance, set start date for the next day. # Remove a few issues from it. # Check Sprint report, you can still see the issues removed from it in the "Issues Not Completed" section. One would expect them to disappear from the report, or at least show in the "Issues Removed from Sprint" section. On the other hand, Burndown Chart will only start burning data when the sprint starts in fact (the next day). # End the sprint. Issues are still shown there regardless.

jonah (Inactive) made changes - 02/Apr/2017 11:59 AM

Link

New: This issue relates to JSWCLOUD-8029 [ JSWCLOUD-8029 ]

Confluence Escalation Bot (Inactive) made changes - 16/Mar/2017 4:32 AM

Labels

Original: affects-server fixme future_sprints todo

New: affects-cloud affects-server fixme future_sprints todo

Confluence Escalation Bot (Inactive) made changes - 20/Feb/2017 12:48 AM

Labels

Original: fixme future_sprints todo

New: affects-server fixme future_sprints todo

Owen made changes - 07/Jul/2016 7:05 AM

Workflow

Original: JIRA Bug Workflow w Kanban v6 [ 908644 ]

New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1550691 ]

Oswaldo Hernandez (Inactive) made changes - 02/Jul/2015 12:53 AM

Workflow

Original: GreenHopper Kanban Workflow 20141014 [ 747061 ]

New: JIRA Bug Workflow w Kanban v6 [ 908644 ]

Load more older events