You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi all. There's a few old threads on here and an old accepted answer that is no longer accurate. I'm going to create a new accepted answer so please let me know if this doesn't address your needs if you are reading this or have posted a comment on here previously.
Details of closed sprints can be viewed within the Reports section of your project or within the Issues page of your project. Note for Team-managed Projects these are both Features that can be turned on and off - details on how to turn them on... here https://support.atlassian.com/jira-software-cloud/docs/enable-reports/ and https://support.atlassian.com/jira-software-cloud/docs/enable-the-project-issue-navigator/
The Sprint burndown chart is in the Reports section and is a great place to view a burndown chart with lots of useful info on scope changes, what was completed, what wasn't etc. Select your sprint in the dropdown. You can also reopen old sprints from here.
If your sprint is quite old and doesn't appear in the dropdown, then you can view the issues that were tagged with a specific sprint in the Issues page. You can add the sprint field (under "More +") to filter by sprint name.
I hope this is helpful.
Thanks for this answer Eoin, though a suggestion might be to just make a Sprint selector dropdown on the "Board" page to easily view current and previous sprints, where the dropdown defaults to the current sprint. That would make it much easier to navigate not having to go into Reports, which is obviously not very clear to users. Again though, appreciate your time and attention to this answer.
I can only see up to 10 sprints back. The rest is not visible and nowhere else to be found. Also not in the other reports. Where can I see the older sprints? This is key for learning purposes; I want to look back and see exactly what we did previously in the Sprint view.
@mheck Keep in mind that personal attacks against Atlassians or other users is not permitted on this platform. Some of your other posts have been removed accordingly and this one is also skirting the line. I understand you're frustrated but please keep our guidelines in mind and stay constructive. Thanks!
@Monique vdB I really struggle to find an attack against anyone it this post. It is a basic and necessary functionality that Your software is lacking. It would be better to focus on fixing that, than trying to avoid answering practical question with emotional response. Bottom line is - You are being payed to deliver a complete software. Your software is lacking core functionality (an that is really important, as we lose time because of this particular problem very often). Users reports the issue. Next step is fixing the issue. That is all.
@Krzysztof Wesołowski hi! I deleted the posts that contained personal attacks which is why you don't see them. Definitely hear the frustration that this gap is causing for people and it's always fine to express that as you did here.
Although I'm not on the Jira team myself, I will try to get an update on this feature for you from someone who is.
Go to Reports -> Sprint burndown chart (not available for all clients??)
Choose sprint from dropdown. (Ours only goes back to the beginning of this year.. nothing earlier than that)
Scroll down. Issues are grouped by : Issues added, Issues incomplete during sprint, Issues Completed.
Choose next print from dropdown.. etc..
Not intuitive, but workable. Hope this helps others.
You're correct that there's no way to currently do this in next-gen projects. We're really sorry for the inconvenience and while we are building up more capabilities in next-gen to support more ways of working, we can also do a much better job of setting expectations for what's available and not yet available in the new project types before creating them.
It would be helpful to understand what you're trying to use the sprint report for, if possible. Is it to reopen or edit a sprint? Access and view the completed work in the sprint?
It's probably not the information you're looking for that you would typically get from the sprint report, but as a workaround that might help unblock some actions for you, you can find and edit issues in any sprint by navigating to the Search page, adding the "Sprint" field in the "More" dropdown button, and selecting your desired sprint name. This will give you all the issues in that sprint which you can edit as necessary from there (either individually or via "bulk change" in the top right). Hope that helps, and sorry again for the inconvenience - we're working hard to improve!
Product Designer, Jira Software
+1 that is would be useful to have the 'Sprint board' not only for the 'Active sprints', but also for previous sprints.
Currently tickets in previous sprints are kinda lost in the Jira system.
And while the tickets are visible in the sprint report, the list of tickets looks very different than how the sprint-board looks. For example the 'lanes' are all gone.
One way I get to previous sprints (YMMV) is to:
From here you can see a table of issues and sort by column headings
I like this path as more information is presented and is very configurable. You don't get the swimlanes as such but you can tailor the columns easily. Give it a go!
Three years and counting...
I just want to understand: if I get a paid plan, do I get this functionality?
This seems so basic I can't really believe anyone would pay for Jira, so it must be there (is it?) but, you know, at this point, I really don't know what to believe any longer.
I think this issue is not solved. If in planning view, we want to see what was done in the previous sprints.
This is very basic feature and just a shame that Jira does not have it. Actually it's a reason not to use it - but we have to, because everybody uses it.
Or do we just not understand the philosophy to use Jira?
When it comes to moving to a classic project, it should be noted that "classic projects" was the legacy term for "Company Managed Projects" (whereas the legacy term for "Team Managed projects" was "next-gen").
It is possible to migrate a project from Team Managed to Company Managed, and vice versa.
The process is outlined here: https://support.atlassian.com/jira-software-cloud/docs/migrate-between-team-managed-and-company-managed-projects
Hope this helps!