I have sent myself down the rabbit hole with this one and can't come up with a solution. I have a main issue that when approved it creates a linked issue. At that point the main issue status is transitioned to Pending and a reason of 'Awaiting Procurement'.
What I want to do is when the linked issue is 'Rejected' or 'Completed' I want to transition the main issue back to In Progress.
I am just not sure what to do with the automation to perform the check on the linked issue to update the main issue status.
Just can't figure out where to start with it.
It might be easier to trigger this off the linked issue rather than pulling in the info from the linked issue.
So the trigger could be Issue Transitioned to Rejected or Completed, you could add whatever conditions you need (any of the systematic fields/values set on creation of this issue should work here), then if you add a related issues branch (selecting Linked Issues, then add the associated link types). You could then add any conditions to this branch, which would be conditions against your main issue which you are actioning, and then add the Transition Issue action under this branch.
Hope this helps!
@Steven Lees-Smith Hmm they should be there, some thing you may want to check:
I am creating the automation in the Procurement project which is the linked issue.
The transitions in the first step are from the procurement workflow, but the 'transition the issue' is still only showing the procurement status, I thought if I said 'For Linked Issues' it would pull in the status from the main issue.
Ah okay, so what you will need to do is go to the global automation section (Settings > System > Global automation) and create your rule here, as otherwise it won't pull through the statuses of the linked project.
Under 'Rule Details' you will need to select 'multiple projects' from the Scope dropdown, and select both the Procurement project as well as the other project which issues will be linked to. This should then pull through the combined list of statuses of the workflows in both projects. Once the rule is saved, this will then appear in both projects under the project's automation rules section, as it is scoped to both projects
Based on your screenshot, I would also recommend limiting the branch to just the single branch type that you have configured in your automation rule which triggers the link in the first place, as well as maybe add a 'project = main issue project' condition within the branch, just to ensure that no other issues linked to the Procurement project issues are actioned by the rule