Sprint states in your plan

Your plan uses five different sprint states: 

• past sprints

• completed sprints

• active sprints

• future sprints, and

• projected sprints

Past sprints

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.

Completed sprints

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.

Active sprints

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.

Future sprints

Any sprint that already exists in Jira 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 board. If you don't set a date in Jira, dates of future sprints are inferred based on your capacity settings and issues that have both the start and end dates set. 

Projected sprints

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.