• Products
  • Documentation
  • Resources

Schedule issues in your plan according to sprints

This page refers to the advanced planning features that are only available as part of Jira Cloud Premium and Enterprise.

We have a separate section for documentation about the project timeline that’s included in Jira. Go to the documentation for the project timeline in Jira.

 

Sprint dates only apply to Scrum teams.

Along with scheduling issues by releases or set dates, you can schedule issues based on the sprint to which it’s assigned.

To infer dates from sprints or releases in your plan:

  1. Select Plan settings from the left side navigation.

  2. In the Scheduling tab under the Inferred dates section, choose which dates you’d like your plan to auto-populate when issues don’t have start and end dates. Choose from:

    1. None

    2. Sprint dates

    3. Release dates

Once configured, you can schedule issues according to sprint dates provided the issues have a sprint and team assignment but no start or end date. For issues that are part of a team-managed project, sprints must be enabled in that project. If their parent project doesn’t have sprints enabled, they won’t show in your plan. Find out how to enable sprints in team-managed projects.

When using sprint dates in your plan, the length of the schedule bar in your timeline is based on the sprint start and end dates. The values in the start and end column in the date fields section will have the sprint lozenge S next to them, as shown below:

Using Sprint Dates in Advanced Roadmaps for Jira Software Cloud

From here, you can then change an issue’s dates manually without changing its sprint assignment. However, if the new dates fall before or after the sprint, you’ll see a warning.

When a sprint is completed, it will appear as finished on the last day. This prevents sprints from overlapping on the timeline and applies whether your issues are scheduled manually or through sprint assignment.

Still need help?

The Atlassian Community is here for you.