On this page:
How does Power Admin detect the priority usage?
This document explains how Power Admin detects how and where a priority is used in a Jira configuration.
Priorities → Projects relation
The usage in projects is determined by the usage of priorities in priority schemes and workflows.
Power Admin detects if a priority’s dependent priority schemes and workflows are associated with projects. Power Admin then will show that the priority is configured in the dependent priority schemes' and workflows' projects (Projects counter in the Summary section).
For example, say you have a priority added to a priority scheme. If the priority scheme is assigned to a project, Power Admin will show you that the priority is part of that project’s configuration.
Priority usage in workflows
Dependency is detected if a workflow participant's property refers to a priority (by name or id).
Priority usage in priority schemes
Dependency is detected if a certain priority is added to a priority scheme.
Priority usage in Agile boards
Dependency is detected:
If the board's JQL entries refer to a certain priority (reference in Saved filters, Cardcolors, Quick filters, Subqueries, Swimlanes).
If the card colors' configuration is based on a certain priority.
Priority usage in filters
Dependency is detected if a filter’s JQL query refers to a certain priority.
Priority usage in Service projects
Dependency is detected when the priority is referred to in Request types, Queues, SLAs, or (Legacy) Automation rules. Usage detection happens when the Service Projects' Cached Index is generated for the first time or when it’s refreshed.