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.
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.
This page refers to Advanced Roadmaps, which is a cross-project planning tool only available as part of Jira Software Cloud Premium and Enterprise.
We have a separate section for documentation about the project roadmap that’s included in all Jira Software plans. Go to the documentation for project-level roadmaps in Jira Software.
Advanced Roadmaps is a sandbox environment meaning that any changes you make to your plan won’t be committed back to your Jira Software issues until you choose to do so.
Learn how to save your changes in the Review and save changes in Advanced Roadmaps section.
To add a new issue to your plan in Advanced Roadmaps:
Group issues in your plan by None, Assignee, Project, Team, Releases, or Sprint.
navigate to +Create issue at the top of the Scope column or
On your timeline, hover over the destination issue, select the menu, and Choose Create [task type].
Select the type of issue you want to create. If your plan contains more than one project, use the dropdown to select which project to assign the new issue.
Name your new issue then use the checkmark to save.
You can't add issues to external sprints or projects not associated with your plan.
If you create an issue using the + Create issue button, Advanced Roadmaps will place your new issue at the bottom of your current project. If you’ve made a child-level issue (such as a story or subtask), it will be listed under the collapsible x issues without parent heading at the bottom of your timeline until it’s linked to a parent task.
If you create a child issue using the , it will be nested underneath the parent ticket and inherit sprints, releases, and teams values.
Was this helpful?