Skip to end of banner
Go to start of banner

Priority usage

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

On this page:

How does Power Admin for Jira 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 for Jira detects if a priority’s dependent priority schemes and workflows are associated with projects. It will then show if the priority is configured in the dependent priority schemes' and workflows' projects (Projects counter in the Summary section).

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:

  1. If the board's JQL entries refer to a certain priority (reference in Saved filters, Cardcolors, Quick filters, Subqueries, Swimlanes).

  2. 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.

  • No labels