Common configurations for Jira administrators before using Plans
This page refers to the advanced planning features that are only available as part of Jira Cloud Premium and Enterprise.
You can start using Plans straight away with no extra configuration. But while not required, administrators have the power to configure it based on how their teams work.
The processes described in this section are only possible with Jira administrator permissions.
Configure hierarchy levels above epics
By default, Jira comes with Epic as a level 1 work type, and Story as a level 0 (subtasks are considered -1 or below Story). As part of your Jira Premium and Enterprise subscriptions, you can add levels above 1 and use these extra levels to track your organization’s larger initiatives in your plans and unify cross-project work. Some common work types are Legend, Odyssey, or Anthology. Or maybe you wanna go crazy and name your higher hierarchy levels things like Monolith, Deity, or Omnipotence. It’s truly up to you.
Find out how to configure custom hierarchy levels in Jira
Actions from your plan in Jira audit logs
Administrators can track some actions from plans in the Jira audit logs. The following actions are included in your audit reports:
when a plan created or deleted
when scheduling configurations are changed
when work sources are added or removed, and;
when an exclusion rule is changed
rename, create, or delete a hierarchy level
move a work type between hierarchy levels
These can’t be edited or changed.
Was this helpful?