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 Version History

« Previous Version 6 Next »

This custom field streamlines the process for users or customers to efficiently prioritize issues or service requests. Priority is determined through a straightforward evaluation of two key dimensions: "Impact" and "Urgency."


Field configuration

Before starting the field configuration, please follow the instructions for creating custom fields

Create a Custom Field

Step 1: Set a name and description

Provide a good name for the new custom field. Make it descriptive, concise, and easy to understand for others who will use it. Avoid using ambiguous or overly technical terms.

Step 2: Setup size and color based on value

The field allows you to choose from a pre-defined set of field sizes.

You may also set different colors for different values.

The priority value is derived from the following matrix, considering the dimensions of "Impact" and "Urgency".


Field view and edit

Set dimensions

You have the flexibility to establish priority levels by adjusting the "Impact" and "Urgency" using a slider, ranging from "low" to "high".

Preview


Related Use Cases

WSJF (Weighted Shortest Job First)Calendar field


Jira Service Management (JSM)

Before you can add a custom field for Jira Service Management (JSM) projects, you first need to setup the custom field

https://help-seibertmedia.atlassian.net/wiki/spaces/ACF/pages/46399542/Priority+Matrix#Field-configuration

Then follow this guide to use the field in the request form or the portal view

Add Custom Fields to Jira Service Management


JQL expression

The Priority Matrix field has three fields that can be accessed.

${fieldName}.priority: number
${fieldName}.impact: number
${fieldName}.urgency: number

Example: a search for all issues with the highest priority (1).

"Priority Matrix.priority" = 1


Data Structure (Automation)

To ensure accurate calculations, it's essential to set both the impact and urgency values when configuring the priority. Failure to do so may result in inadvertent overwriting of value during recalculation processes.

To set the value via automation, you need the following object structure, where value marks the priority.

{
  "impact": [0-2],
  "urgency": [0-2],
  "value": [1-5]
}


  • No labels