Configure your instance

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

The changes on this page require Jira Software Administrator access.

In this section, we'll cover how to do the following:

Surface fix versions in Jira Software issues

What are known as releases in Advanced Roadmaps are known and treated as fix versions in Jira Software. If the fix version field is hidden in your issues, the releases you set in your plan won’t display in the corresponding issues. In order to view and make changes to these fields, they must be added to your Jira Software instance by an administrator.  

To display the fix version field in Jira Software:

  1. Navigate to the Jira Software admin panel using the  icon in the upper right and choose Issues.

  2. From the menu on the left, select Field Configurations, then the field configuration of interest.

  3. Select Configure, then find the Fix Version field.

  4. In the Actions column, select Show.

Each time a release is set for an issue in your plan, and you save this change to Jira Software, the release will appear as the fix version for the corresponding issue.

Add custom fields (including components and labels)

Before you can assign labels and components to issues in Advanced Roadmaps, they first must be defined in Jira SoftwareLearn how to add custom fields and configure them in the Jira Software Admin documentation. 

Data in these custom fields will be saved to your Jira Software issues, but won’t be visible until the fields are added to your instance.

Add custom dates

To use custom dates in your plan, you must add the custom date field to the schemes of all the projects associated with the issue sources of the plan. Once selected, the custom dates will be displayed with the date lozenge (D) in your timeline.

Change hierarchy settings and add custom hierarchy levels

To better track your plan’s progress, issues are grouped into different tiers referred to as hierarchy levels.

The hierarchy in Advanced Roadmaps is inherited from the default issue types in Jira Software:

  • Epic — A large body of work that can be broken down into smaller issues such as stories, and tasks. In a plan, epics represent a significant milestone or deliverable. The work contained in an epic can be assigned across multiple teams.

  • Story — Stories and tasks are issues that represent work that needs to be completed. These issue types can be assigned to specific teams.

  • Subtask — A granular piece of work required to complete a story, or task. In Advanced Roadmaps, subtasks can’t have teams assigned specifically to them (they inherit the team assigned to the parent issue).

In your plan, you can select which hierarchy levels you want to view using the hierarchy range selector as discussed on View your plan.

Custom hierarchy levels

If you plan and track work across an organization, you’ll need to create hierarchy levels above epics. For example, you can create an Initiative or Legend hierarchy level to represent company-wide goals. When positioned above the epic level, the initiative can be used as a container for epics. Bug fix and Improvements are two common examples of custom lower hierarchy levels that help track day-to-day tasks.

Adding hierarchy levels to your plan is a two-step process. First, you must configure the hierarchy level in Jira Software:

  1. Navigate to the Jira Software admin panel using the  icon in the upper right and select Issues > Issue types.
  2. Select Add issue type on the right side of the screen. In the modal that appears, choose whether you'd like to make a 
  3. When you're ready, choose Add to save your new hierarchy level.

Once you've added your new hierarchy level to Jira Software, you can now add it to Advanced Roadmaps

To manage or add custom hierarchy levels in your Advanced Roadmaps plan:

  1. Navigate to the Jira Software admin panel using the  icon in the upper right and select Products.

  2. In the menu on the left, select Advanced Roadmaps hierarchy configuration.

  3. Select or remove hierarchy levels you want to include in your plans.

  4. Select Save changes.

Configure Dependencies

In order to use dependencies in your instance, Issue linking must be turned on which we cover in the Configure issue links section of this page.

Advanced Roadmaps comes with several predefined issue links which you use to define dependencies. You can create the following types of dependencies:

  • Blocks
  • Clones
  • Duplicates
  • Issue split
  • Problem/Incident
  • Relates

You can also swap the dependency order, and use custom dependency links that have been created in Jira Software.

To change how Advanced Roadmaps handles dependencies: 

  1. Navigate to the Jira Software admin panel using the  icon in the upper right and select Products.
  2. Go to Advanced Roadmaps dependencies. Add an issue linking type using the dropdown menu, or remove it with the x that appears in the box. Use Swap on the right side to invert the dependent relationship. 
  3. Select Save changes.

These changes will apply to dependencies in all plans in your instance. 

For more information about issue links, see the Link an issue page in Jira Software Support.

In order to use custom issue links in your Advanced Roadmaps plan, they must be created and defined inAdvanced Roadmaps.

To enable and set up issue linking:

  1. Navigate to the Jira Software admin panel using the  icon in the upper right and select Issues.
  2. In the left hand sidebar, select Issue linking under Issue features
  3. Make sure that Issue linking is set to ON. If it's not, select Activate to enable it.
  4. Once activated, you can edit the Name, Outward description, and Inward description of an existing issue link by selecting Edit from the right column. Use Update to save your changes.
    1. To add a new link, define the name of your new issue link and the descriptions using the fields under the Add New Link Type header. Use Add to save it. 

Show the Teams field in Jira Software

While the Teams field is a default field in Advanced Roadmaps, it’s considered a custom field in Jira Software. In order to save and edit values you add to the Teams field in Advanced Roadmaps to Jira Software issues, you'll first need to add this custom field to the corresponding Jira Software project.

  1. Navigate to the Jira Software admin panel using the  icon in the upper right and select Issues.

  2. From the menu on the left, select Custom fields, and find the Team field in the list of fields.

  3. Select Screens, and select which screens to which you want to add the Teams field.

  4. Select Update to save your changes.

Each time a team is assigned to an issue in your plan, and you save this change to Jira Software, the team field will appear in the corresponding issue.

Last modified on Mar 23, 2021

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.