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.
Along with scheduling issues by sprints or set dates, you can schedule issues based on the release to which it’s assigned.
To change which dates Advanced Roadmaps uses in your plan:
To infer dates from sprints or releases in your plan:
From the Roadmap view, navigate to settings using the next to your plan name > Configure.
In the Scheduling tab under the Inferred dates section, choose which dates you’d like Advanced Roadmaps to auto-populate when issues don’t have start and end dates. Choose from:
Once enabled, you can schedule issues according to the release dates the issues are assigned to a release, but have no start or end date. From here, you can then manually adjust an issue’s dates without changing its release assignment. However, if you move an issue beyond the release date, your release will fall off-track and the icon will turn red.
In order to use this setting, releases in your plan need to be scheduled using Fixed dates. If your releases uses As soon as possible, After all issues are completed, or Relative to a previous release as a start or end date, the schedule bar fades out indicating that it can’t be determined.
The Start date and Due date fields will have a R lozenge next to them, as shown below:
Was this helpful?