I want to know which issues are getting spill over or carry forward from one sprint to another.
Let suppose we want to know issues which are carry forwarded from sprint 1 to sprint 2. Please help on this
Hi @sai chinamuthevi ,
You can use a combination of JQL Functions to achieve that, such as:
Sprint in openSprints() AND Sprint in closedSprints()
This will give you any task that has been carried over from any closed sprint to any open sprint.
But if you have some specific sprint in mind, then just remember that Sprints field is a list of Sprints, so you can simply query:
sprint in ("sprint 1", "sprint 2")
find more here
Hope it helps!
it gives me list of issues that are in combination of both sprint 1 and sprint 2 but i want issues which are carry forwarded from sprint 1 and closed in sprint 2. Jql is returning correct only but i see discrepancy of results in burn down chart. Don't know why?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @sai chinamuthevi ,
The only way to get a somewhat consistent picture of the Uncompleted Scope in a sprint using native JIRA is the Sprint Report. However, even the Sprint Report doesn’t provide the full picture. If you have Removed Scope within a sprint, the Sprint Report won’t show it as Uncompleted Scope.
If you would like a fine-tuned solution without the issues I mentioned above, you can use the app I developed - Multi-team Scrum Metrics & Retrospective.
The 'Uncompleted Scope' metric covers your request. The app also allows users to conduct in-place retrospectives to prevent the same issues or reasons from recurring in the future.
Statistics:
Best regards,
Alexey
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.