...
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.
Plans has a range of options/actions and settings to create and manage a plan
(1) Manage your view
(2) Modify your view
(3) Issues in your plan
(4) Issue values in columns
(5) Timeline schedule bars, dependencies, and releases
(6) Clean up your plan and save changes in Jira
In YME Jira we use a template filter that The template filter selects the following data per team:
"Yamaha Team" = TEAM OR "Yamaha Team(s)" = TEAM ORDER BY Rank DESC
...
The following data can be set as excluded in Plans configuration:
It's recommended to use your 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.
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)
...
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.
...