Page History
...
Note is a field specifically used for Roadmaps, to easily note and read comments about progress, roadblocks, or dependencies.
Hierarchy
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) , Strategic Theme (YPB), Milestone (YNSEU),
...
Level 3:
...
Initiative (
...
YPB) , Feature (YNSEU),
...
Project (
...
YPM)
All others levels are used in Jira Software projects.
Story level = Story, Enable Story, Task, Spike, Bug, Defect and for Jira Service Management Incident, Service request, Service request with approvals etc.
Hierarchy linking is done through epic link or parent link. You cannot skip a level so an epic must always be linked to a Initiative, Feature or a Project.
The Hierarchy can be manually selected for Teams, the Basic View is Epic to Story level:
...
Defect
Incoming dependency: defect of
Outgoing dependency: has defects
Dependency
Incoming dependency: Dependency from
Outgoing dependency: Dependency to
View dependencies in the Dependencies report tab
...
Overview
Content Tools