I have two projects - Design and purchasing. When the design workflows gets to a certain status I want it to automatically transition the status of the purchasing task it is related to (by links). Is this possible with automation add-on?
Yes you can do this with Automation for JIRA using the 'Related issues' action. You'd have to setup a rule like this:
Because this rule touches multiple projects, you'll have to configure it as a 'Global' rule in global administration in the System > 'Automation rules' section.
Hope this helps!
Is it possible for Jira Project Automation (I have the extended, payed version) to not have access to cross-project links when one of them is ServiceDesk? I am following the very steps you indicated to Sheena above (see picture).
in my case
Sheena's Design = DAIL
Sheena's Purchansing = MITSD
and, for linked Issues which happen to be in my MIT-S[ervice ]D[esk] project the rule falls short of applying with "No related issues could be found". This is pretty surprising - the more so as I put myself as the actor and the owner of the rule and I am an agent authorized to use the Service Desk (MITSD) project. Please tell me I am doing something wrong :).
It seems to be an issue not with Service Desk, but with cross-project linked issues detection (the rule branching).
Additionally, if you look at my second snapshot below, I have a case where an issue (Dail-442) is linked to a "close" (i.e., same-project) Dail-443 issue and to a "far" (= different project) one, MK-95. When the same rule applies, at 13 sec. interval:
Dail-443 (the same-project sibling) is considered worthy of being a "match" for the LInked Issues rule (see highlights in green, 12;24;31", with success and follow thru with the Then-action.
MK-95 (the different-project sibling) is considered a non-match (see in red, same minute @ 18") and No-Actions-Performed.
Thanks for the detailed screenshots.
So it looks like your rule is setup correctly in global admin so it should be able to find related issues in another project.
Can you check your releated issues action though to see if the 'Only include issues that have changed since the last time this rule executed' is checked? You might have to uncheck this.
I believe the second screenshot with issue DAIL-442 shows something different - the first execution with id 799, DAIL-442 didn't match the JQL condition, so it probably wasn't in the 'Done' status yet. The rule never executed the related issues action. (In action details it only mentions the JQL condition)
Hope this helps.
Thank you for your attention (and prompt answer).
I figured out that the rule was, quite contrarily, setup _Not_ in the Global context -my bad- but in the DAIL[Y] project - as one can see from the first screenshot (see the blue Chrome window, under my Exo-ops bookmark). That was the simple reason why it was not working with cross-project linking :). Sorry for randomizing you with a "by design" issue :).
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Atlas Camp is our developer event which will take place in Barcelona, Spain from the 6th -7th of September . This is a great opportunity to meet other developers and get n...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs