Hi there!
We've recently migrated from an on-premise JIRA server to the Cloud, and with the use of automations, it's really changed the way we do things, however, it doesn't come without a very steep learning curve.
I would like to set up a rule using JIRA Automation to transition a parent issue (of a specific issue type), when an issue is linked to the parent issue.
My requirements are:
I've been trying to set this up, but I'm unable to get the parent to transition to the correct status (or at all). I expect that my trigger or conditions are incorrect.
I've started with trigger "when: issue linked", and then a condition to only action this rule on a specific issue type. Initially didn't have the condition in place, but even this did not help.
I then have a branch, so that I can potentially work with the 3 statuses I need the parent issue to transition to, but the rule is never triggered.
I've added a couple of screenshots... one is the current rule set up I have (only using 1 branch/status at them moment. The other is the log results I get, where LONOPS-567784 should be the parent issue and LONOPS-567778 should be the linked issue.
Any help would be appreciated! Thanks in advance!
There's no parent issue when you link issues of the same level, that most likely the root of the problem. So when you link issues, one issue is a Source issue (with an outward link, for example 'blocks') and the other is a Destination issue (with an inward link, for example 'is blocked by'). You can see which issue is which in your action details.
If you select the issue linked trigger, the main issue of the rule is always the one with an outward link. To transition this Source issue there's no need to use branches, you should select if-else condition in your case and add your status conditions.
If you want to transition the other issue, you should use the Destination issue branch. You probably will have to create three similar rules with different conditions inside the branch (unfortunately we can't use if-else inside branches).
Hope this helps, Alisa
Thank you very much for this explanation, it makes complete sense...
I will take a look at this as soon as I can and let you know how it goes
Thanks
Jean
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I've updated the automation as suggested and it works very well!
All I need to do now is to send a notification if the transitioned issues are in their current state after 24 hours!
Thanks
Jean
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Show up and give back by attending an Atlassian Community Event: we’ll donate $10 for every event attendee in March!
Join an Atlassian Community Event!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.