Table of Contents
In Jira it's possible to plan work on a timeline. This feature is called Jira Advanced Roadmaps and can be found in the top bar under "Plans".
The template Roadmap looks like this, allowing teams to plan their work per quarter and report out to management easily:
Every logged in Jira software user can view Roadmaps. Only those with specific Jira Advanced Roadmaps access will be able to edit Roadmaps.
If you want to have a Roadmap created for your team, you can request one through a Service Desk ticket. You will then receive a template Roadmap and Jira Advanced Roadmaps edit access.
The template filter selects the following data:
"Yamaha Team" = TEAM OR "Yamaha Team(s)" = TEAM ORDER BY Rank DESC
Note: Only if the team is able to set this same filter as their scrum board filter, Roadmaps will unlock Sprint Planning features.
The following data is excluded in Roadmap configuration:
The Hierarchy on the Basic View looks only at Epic and Story level:
The Roadmap allows filtering, where a selection of multiple filters results in an AND statement. So selecting Team = Awesome and selecting Assignee = John, means that both statements need to be true.
It's recommended to use this board to fill/correct the Basic View fields:
Note: the Progress bar will calculate based on underlying items, excluding anything completed longer than 14 days ago.
If you make any changes in Jira Advanced Roadmaps, these are not automatically saved into the Jira database.
You need to Review Changes made in the top right corner, once you are happy with your plan and wish to commit it.
Be warned: If you do not Review Changes, then the Roadmap will remain unpublished, and the data on your scrum board will differ.
It's possible to drag and drop items, to change the relative rank between items, or to create issue links.
When you move a Story underneath an Epic, the Epic Link will be created on the Story (after Reviewing Changes).
When you move an Epic underneath a Project, the Parent Link will be created on the Epic (after Reviewing Changes).
Dependencies show the relationship between issues in your plan, such as contingencies and blockers.
The following issue link type will be treated as dependencies in plans.
Blocks
Incoming dependency: blocks
Outgoing dependency: is blocked by
Defect
Incoming dependency: defect of
Outgoing dependency: has defects
View dependencies in the Dependencies report tab
Manage your decencies under the Dependency Management view.
Atlassian documentation