Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Set priority based on custom field in JSM

Joshua Dumas
Contributor
December 21, 2023

We're using JSM as a request system and JIRA as our development and when linked issues get created from the request I need to check a custom value on the request (let's call it "Mandate") and if it's set to Yes I need the newly created linked issue to have a priority of High. There are also situations that the field (Mandate) is updated after the linked issues are created 

What would be the best way to accomplish this?

3 answers

3 votes
Giovanni Melai
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 21, 2023

Hi @Joshua Dumas

you can use Jira Automation. Since it's cross-project automation you need to create it as a global rule.

You should be able to use one rule with the trigger "Multiple issue event" and select Create and Update. You must check when an issue is created or updated in the development project/s.

Now you need to use conditions to check if there is a JSM issue linked to it, if it's true you can read the "Mandate" field from that issue and update the Priority based on the outcome.

Of course this is just a general idea on how to do it. 

I hope this helps

2 votes
Dirk Ronsmans
Community Champion
December 21, 2023

Hi @Joshua Dumas ,

At first glance this should be easily possible with Automations.

If you set the trigger based on the "Mandate" field changed (and maybe a 2nd one for issue created (depending on when the field is set)), you can then use the Edit Issue action to set your Priority field.

0 votes
Joshua Dumas
Contributor
December 21, 2023

In automation, how would I check if the mandate field in a linked issue of type X is equal to Yes?  This is what I currently have - the if condition Mandate I believe would be checking the triggering record (the development tasks) fields - mandate exists on the parent issue

 

2023-12-21 09_57_42-Automation - Jira.png

Giovanni Melai
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 21, 2023

Well, thinking about it is better to start with the "Field value changed" trigger, something like this (I selected Components since I don't have the field Mandate):

Screenshot 2023-12-21 at 16.46.44.png

Then you should not use the Branch but the "Related issues condition" to check the Mandate field with a JQL (Mandate = Yes), and then you can use the action to Edit the Priority. Something like this:

Screenshot 2023-12-21 at 16.56.19.png

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events