I am running into a recurring issue with the sprint report not accurately showing ALL of the JIRA tickets that were removed from the sprint. To be clear, it does show some of the tickets that were removed from the sprint, but not all of them. This is causing issues with being able to use the report for our sprint review meetings and I find that I am having to keep track of the original tickets in a side document.
I'm not sure what the root cause is, and maybe it's operator error.
Dear @Jason Everson,
can you please tell us, how you removed the issues from the sprint?
So long
Thomas
From the active sprint board, I select the JIRA ticket so it displays in the side detail. From the side detail, I use the menu to "Remove from Sprint".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear @Jason Everson,
as I cannot reproduce your behavior on my instance I can just guess for protential reasons:
So long
Thomas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thomas,
Thanks for continuing to help with this issue. Here are my responses:
Zeroing in on a specific issue that is absent from the Sprint Report, I have the following information:
We have been working on this ticket for a long time, and for various reasons, we have not been able to complete it yet. Below is a list of the sprints that the ticket was on when the sprint was started and which sprint reports correctly show that the ticket was removed.
Sprint 3 - sprint report shows it was removed
Sprint 4 - sprint report shows it was removed
Sprint 5 - sprint report shows it was removed
Sprint 6 - sprint report DOES NOT show that it was removed
Sprint 7 - sprint report DOES NOT show that it was removed
Sprint 8 - active sprint with the ticket on the original plan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear @Jason Everson,
you already know, that something different goes wrong, when one issue is shifted for more then 2 times to following sprints, right ;)
What you decribed sounds like a bug. Probably there is a hard coded counter for more than 4 removals - I don't know. I recomment, that you contact the Atlassian Support. Eventualy you can find an already reported bug on https://jira.atlassian.com.
So long
Thomas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm also finding this with a ticket that has moved multiple sprints. Is this a bug that I can follow?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.