This should be treated at a HUGE issue, it undermines the core of Scrum and Sprints as it not only hides information but also falsely presents data as correct when it's not.

If we remove a story from an active sprint which was previously in a "Completed sprints" then Jira "forgets" it was ever in the current sprint! This is causing real issues with the use of your product. If we remove a story from an active sprint which was previously in anther "Completed sprints" then Jira "forgets" it was ever in the current sprint!

This means when mid-sprint if we swap a story from the current sprint with the backlog, then the burndown, sprint report, etc. makes it look like we are just adding new stories to the active sprint without taking anything out! Total loss of control.

I.E. Take out 4 points, add 4 points, you expect the burndown to stay at the same level. But no, the burndown goes up and there is Absolutely NO record of this in the "Sprint Report", "Burndown Report" the only place this information is shown on it on the story's Activity "history" tab, shown as: "Sprint Sprint 8 - 25th April, Sprint 11 - 6th June [ 21214, 21360 ] Sprint 8 - 25th April, Sprint 12 - 20th June [ 21214, 21459 ]""Rank_DUP Ranked lower"

These removed stories do not show in the "Issues Removed From Sprint" "Sprint Report".

Anyone know of a workaround? The only one I can think of is to zero out the story points of the story and leave it in the active sprint (make a note of the story points in the comments of the story). this was at least if we add a new story to active sprint it will keep the burndown at the same level.

If anyone else can think of a way to hack the system to bodge this issue, please let me know, I have messed around with it and think it may be something to do with the filter rules Jira is using to show what’s in sprint. I.E. Only show stories removed if they were not already in a completed sprint.

Jira Software server

Jira v7.13.1 with JIRA Agile v7.13.0-DAILY20190110202320

Hi Atlassian people!

Any updates to this ?
Will this be fixed in 8.x ?
Would it be possible to get triage decision do or not to do fix - annoying to see that reporting bug is low priority and no real updates for 2 years.

The same issue (v7.6.8)

Added from previous sprint issue can be removed from the current sprint and whole burndown chart will be redrawed as that issue has never been in scope.

But in issue's history there is a changing of removing sprint.

Same issue in v7.2.4.

The team has lost faith in any metrics derived from Jira and that loss of faith is impacting our agile transition as a whole.

We are facing same issue in Jira 7.6.8

If it is resolved in cloud version (JSWSERVER-13810 ), how much time it will take to implement same in stand alone versions?

I see some negligence when come to stand alone server bugs.

Can we close this issue as a duplicate of JSWSERVER-14984?
This would help the issue get to a critical mass for Atlassian to notice.

Severity and priority should be raised!  This brings the integrity of the reports into question and makes it difficult to trust them from a sprint management and tracking perspective.

Affects 7.4.4 server as well

Please fix!

We have now hit this problem.

The motivation for our organisation to stay with JIRA is greatly reduced if we cannot rely on the Agile reporting offered.

Really saddened that this is seen as a minor issue. After I told some of my teams about this bug their first question was "so what are we going to use instead of the sprint reports?".

This makes reports almost completely unreliable and people have lost faith in them. This is 100% repro steps and impacts the trust in the product. Hopefully it gets fixed soon.