Automate priority change if linked issues exist when changing status

[Mark Farmer]

Hi,

I work with a lot of test cases and have automated much of the creation process. I now want to be able to automate the priority in order to change it when the issue moves to a new status and if the issue has linked issues.

ie:

Issue A has Issue B linked as a blocker or test. Issue A moves into In Progress status. Issue A's priority needs to change. 

I can't seem to get any logic I try to work.

[Jack Brickey · Accepted solution]

Hi @Mark Farmer , see if the following is close to your goal...

P.s. I see you are on Premium? If so I highly recommend trying out the AI feature for creating rules as I have found it quite useful.

[Mark Farmer]

Hi Jack,

I tried something similar and it was changing the priority of the linked issues rather than the ones where the status was changing.

[Mark Farmer]

I've asked if we can use the AI feature and I'm told I can't (some political machinations further up the hierarchy I suspect) :D 

[Jack Brickey]

😒 

[Jack Brickey]

Keep me posted if the above works

[Jack Brickey]

The above rule will only change the priority of the trigger issue not the linked issues. If you see something different please advise and share audit log.

[Mark Farmer]

Hi Jack, I've changed to this rule and now nothing's happening. The rule runs but it seems to think the ticket (CHDT-511) doesn't meet the criteria. The linked issues don't change now though so that's a bonus.

[Mark Farmer]

[Jack Brickey]

Can you share the details of the condition component? Are you choosing a specific link type in that condition? Have you verified that the linked issues are of the type in the condition. 

[Mark Farmer]

[Mark Farmer]

They're all linked as 'tests' and that's the condition I've aligned it to. 

[Jack Brickey]

Could you try changing the condition to be any link type and test?

[Mark Farmer]

[Jack Brickey]

Hi @Mark Farmer , so I just did a test and it worked fine. one thing I note in your las image is that the linked issues are in a different project. Did you set the rule to be multi-project or global?

[Mark Farmer]

Hi @Jack Brickey I think this is the issue. I've not the permission to make the change but I've submitted a request to our admin team to change it to multi-project. Once it's done I'll come back and let you know!

[Jack Brickey]

Yes that is the issue for sure.

[Mark Farmer]

Hello! Finally got the update, adjusting to multi-project worked. 

[Jack Brickey]

Thanks. Please consider accepting one of the answers here that helped you zero in on the cause.

[Bill Sheboy]

Hi @Mark Farmer -- Welcome to the Atlassian Community!

What is the scope of your rule: single-project, multiple-project, or global?

A single-project scope rule can create / clone issues into other projects, but it cannot access them in any other way.  That is likely why no linked issues are found in your rule condition.

Please try working with your Jira Site Admin to change the rule scope to multiple-project, and select the specific projects needed.

Another possible cause of this symptom is link-direction not matching the condition.  You show the "tests" linkage.  What is the link name from the other direction?

Kind regards,
Bill

[Mark Farmer]

Hi Bill! Thanks for the warm welcome!

I've had to submit a request to our admins to change the rule from single to multi-project, hopefully this will resolve my issue. I'll come back and let you know!

[Tomislav Tobijas]

Hi @Mark Farmer ,

Based on the following:

ie:

Issue A has Issue B linked as a blocker or test. Issue A moves into In Progress status. Issue A's priority needs to change. 

You can maybe try using the issue transitioned trigger followed by a condition that checks if there are linked issues (you can additionally specify to check for certain link types).

Lastly, if the condition passes, update the original/trigger issue > Priority field by using Edit issue action.

I'm not sure if that is something that you're trying to achieve. Feel free to share some additional details if I maybe missed the point.

Cheers,
Tobi

[Mark Farmer]

Hi Tobi,

I tried a similar approach but it was changing the priority of the linked issues. What I'm aiming for is changing the priority of the issues that are changing status

[Tomislav Tobijas]

@Mark Farmer If I'm looking at the screenshot provided in another thread, this rule should update the Priority field only for trigger issue (issue that changed the status), and not the Priority fields of linked issues.

Can you share the most recent rule, together with the audit log, once is successfully executed?

[Mark Farmer]

[Mark Farmer]

Apologies for the image surge Tobi but I thought it best to send everything relevant. @Jack Brickey to save duplication :D 

[Tomislav Tobijas]

No worries @Mark Farmer !

By the looks of the audit log, the only 'checked' issue was CHDT-510.

Are you saying that all those linked issues in HE project were updated/their priority was changed? Can you check (and/or screenshot) issue history for those issues?

[Mark Farmer]

It may have been a different variation of the flow I'd tried previous(there's been so many!) using this flow, the priority on the 510 ticket doesn't change when moving to Selected for Execution. If I have another CHDT ticket linked, it does.