MoSCoW

Field Configuration

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

https://help-seibertmedia.atlassian.net/wiki/spaces/ACF/pages/40206400

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: Configure your custom field

In this step you can configure the displayed size of the field

Field view and edit

Edit view

Issue view

Related Use Cases

More use cases are coming soon. In the meantime, check out our other use cases.

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/12255266/MoSCoW#Field-Configuration

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

https://help-seibertmedia.atlassian.net/wiki/spaces/ACF/pages/40009764

Request form

Portal view

JQL expression

${fieldName}.Priority: "must" | "should" | "could" | "wont"

Find further information here https://support.atlassian.com/jira-software-cloud/docs/find-specific-issues/

Example: a search for all issues prioritized with “should“

MoSCoW.Priority = should

Data Structure (Automation)

https://help-seibertmedia.atlassian.net/wiki/spaces/ACF/pages/40009823

To set the value via automation, you need the following object structure

{
  "priority": "must" | "should" | "could" | "wont"
}