Table of Contents
In Jira it's possible to plan work on a timeline. This feature is called Jira Plans, (previously Advanced Roadmaps) and can be found in the top bar under "Plans".
The template Plans 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 Plans. Only those with specific Jira Plans access will be able to edit Plans.
If you want to have a Plan created for your team, you can request one through a Service Desk ticket. You will then receive a template Plan and Jira Plans 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 can be set as excluded in Plans configuration:
The Hierarchy for Plans, project items are grouped into hierarchy levels based on Issue Types.
For YME Jira the following Hierarchy has been setup:
Level 1-3 is used for Portfolio planning:
Level 1: Capability (YNSEU)
Level 2: Programme (YPM) , Milestone (YNSEU), Strategy (YPB)
Level 3: Project (YPM) , Feature (YNSEU), Initiative (YPB)
All others levels are used in Jira Software projects.
The Hierarchy can be manually selected for Teams, the Basic View is Epic to Story level:
The Plan allows filtering, where a selection of multiple filters results in an AND statement. So selecting Team (Yamaha Team/ Yamaha Team(s) = 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 XX days ago. The exclusion rules can be found under the configuration of Plans Settings.
If you make any changes in Jira Plans, these are not automatically saved into the Jira database.
You need to Review Changes made in the top right corner to clean your plan, once you are happy with your plan and wish to commit it.
If you do not Review Changes of your plan the data on your Board will differ from your Plan. Edit Issue Permission for Jira issues in the relevant project is required to be able to save the changes in Jira. |
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