There is not a good, native method to get that information.
Each issue keeps track of all the sprints to which it was added and not removed. If an issue was added to Sprint 1 but not completed during that sprint, and subsequently added to Sprint 2, the the issue's Sprint field will show both Sprint 1 and Sprint 2.
There is no built in method to query/report on the sprint in which an issue was specifically closed. You could infer it by looking at the Resolved date of the issue and the date ranges of the associated sprints, but there is no query or reporting functionality available natively to help with that.
You might want to investigate third party apps in the Atlassian Marketplace that provide more sophisticated querying and reporting functionality to see if any of them can help you meet your requirement. That is not a requirement I've had to satisfy, so I don't have any recommendations on a specific app that will help.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We ran into the same challenge — once a sprint is closed, it’s surprisingly hard to review it in a convenient, board-like way. The native reports help, but they don’t really give that clear “what exactly happened in a few last sprints” view (scope changes, carried over issues, late additions, etc.).
Because of that, we (Tymola) ended up building a small marketplace app called Sprints & Work History that focuses specifically on making closed and completed sprints easier to browse and analyze over time.
If that’s the kind of visibility you’re missing, feel free to check it out. And if you do, we’re very open to feedback — the app was created to solve exactly this pain point, so suggestions from real teams are always welcome 🙂
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.