How can I add an action creating an automation to set specific priorities to a work type?

[Adrian Moreno Vargas]

Dear all,

I am creating an automation.

My goal is to have specific priorities when a specific work type is created.

Trigger: When Work item is created.

Condition 1: Issue Type equals Incident

Add action: (when a new ticket is created as Incident, I need to have selected priorities to be shown)

What action should I set to have specific priorities linked to a specific work item?

Thanks a lot

Kind regards

[John Funk]

Hi Adrian - Welcome to the Atlassian Community!

You would use the Edit Work Item action, then select the Priority field. 

[Jack Brickey]

And to John's recommendation here is an example. You can add additional else conditions as needed.

[Trudy Claspill]

Hello @Adrian Moreno Vargas 

Welcome to the Atlassian community.

Are you trying to limit the Priority values that will be available to select in the Create Work Item dialog, based on the Work Type you select?

If so, that is not something that can be done through Automation Rules. Automation Rules are triggered in response to the completion of an event. So, for instance, when you click the Create button in the above dialog and the issue is actually created in the Jira database, then your rule's Issue Created trigger would get activated. Your rule could then modify the Priority (or any other field, or take other actions) in the item that was just created.

If you want to change the Priority values that are available for selection in the Create Work Item dialog, a different solution is required.

Jira Cloud supports creation of a Priority Scheme that sets which Priority values can be used in a project, but it does not natively support a configuration for Priority values that can be used based on the item type.

If you want to make that sort of change within the Create Work Item dialog shown above, that would require a third party app such as ScriptRunner Behaviours from Adaptavist.

[Jayesh Raghuvanshi]

@Adrian Moreno Vargas 

Set this up with an “Issue created” rule that checks “Issue type = Incident” and uses “Edit issue” to set Priority to the value(s) you want; automation can set the field but can’t change which priority options are shown on the create form itself. To actually restrict which priorities appear, use a Priority scheme at the project level and associate it to the project; schemes limit the available priorities the user can pick in that project, not per issue type

Automation Steps

• Go to Project settings → Automation → Create rule → Trigger: Issue created
• Add Condition: Issue fields condition → Issue type equals Incident
• Add “Re-fetch issue data” right after the trigger to avoid race conditions on creation events
• Add Action: Edit issue → Field: Priority → pick the desired default (e.g., High); use If/Else branches if you have multiple incident variants and want different priorities
• Save and enable the rule, then test by creating an Incident to confirm the Priority is set automatically

Thanks
Jayesh R