Issue type usage
On this page: |
How does Power Admin for Jira detect the issue type usage?
This document explains how Power Admin identifies the usage and dependencies of issue types in a Jira configuration.
Issue type usage in issue type screen schemes
Dependency is detected if an issue type screen scheme configures a relation between an issue type and a particular screen scheme.
Issue type usage in workflows
Dependency is detected if a workflow participant's property refers to an issue type.
Issue type usage in workflow schemes
Dependency is detected if a workflow scheme is configured for this issue type.
Issue type usage in issue type scheme
Dependency is detected if an issue type is part of an issue type scheme.
Issue type to agile boards
Dependency is detected if:
There is a reference to the issue type in the board's JQL entries (Saved filters, Cardcolors, Quick filters, Subqueries, and Swimlanes).
The card colors' configuration is based on the issue type.
Issue type to filters
A filter is shown as a dependency of the issue type if its JQL query refers to this issue type.
Issue type to service projects
Dependency is detected when the issue type 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.