Learn how to set up Jira Software Cloud and integrate it with other products and applications.
Learn how to configure your Jira Software Cloud company-managed projects to suit your agile development processes.
Learn how to create, search, and work with issues in software projects, manage your profile, and more.
Learn how to get started, enable features, and manage and administer team-managed projects.
Create powerful rules to start automating your manual, repetitive processes.
Plan and view work across multiple teams, projects, and releases with Advanced Roadmaps.
A guide on how to deploy and monitor an application built on AWS using Atlassian and third-party tools.
Advanced Roadmaps uses five different sprint states:
future sprints, and
Past sprints are unnamed representations of what past iterations would have been if the sprints existed at that point. They're created based on sprint length and are used for demonstration purposes only. The sprint capacity window won’t appear when you hover over the sprint status bar.
While past sprints are representations of past iterations, Completed sprints are scheduled sprints that have been completed by your team. You can hover over completed sprints to see details, but you can’t change the information.
An Active sprint is the sprint that's currently in progress and has an ACTIVE SPRINT lozenge next to the dates.
When auto-scheduling work in a plan, issues will be scheduled into the next available future sprint, based on the remaining sprint capacity. Issues won’t be assigned to a currently active sprint.
If there’s any unexpected change in a team’s capacity (for example, a team member is sick), you can quickly update the sprint capacity in the active sprint’s menu.
Any sprint that already exists in Jira Software and is scheduled after the active sprint is called a Future sprint and will have a FUTURE SPRINT lozenge next to its name. Dates of future sprints will show on your timeline as defined on the Jira Software board. If you don't set a date in Jira Software, dates of future sprints are inferred based on your capacity settings and issues that have both the start and end dates set.
Any sprints that are projected to take place beyond the scope of existing future sprints will also be displayed in the timeline. These are called Projected sprints and will have a PROJECTED SPRINT lozenge next to the dates.
Was this helpful?