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.
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.
In the Review changes modal, you may see warning icons in the far left column. We recommend resolving these issues before saving your changes to Jira Software.
This issue has been added to an active sprint
If you add or remove an issue from an active sprint, you’ll see a warning in the Review changes modal informing you that this will change the scope of the sprint.
There’s no resolving this issue as it won’t break your plan, but it’s a heads up that sprint capacity will be affected.
Required custom fields in Jira Software issues
If your Jira Software issues have required custom fields, but these fields weren’t added to Advanced Roadmaps, you'll see a warning. Since these fields are required, you’ll need to either add them to your Advanced Roadmaps plan or turn off the required field in Jira Software.
Custom fields not supported for issues types or projects in plan
If you set a value for a custom field that hasn’t yet been set up in Jira Software, you won’t be able to save this change from your plan. If you need this change to be saved, ask your Jira Software admin to configure this custom field in your instance.
Child issues not saved to Jira Software
If you’ve created child issues in your plan, the parent issue needs to be saved in Jira Software as well. Since the child issue is dependent on values inherited from the parent, the child issue can’t be saved on its own.
Was this helpful?