Hi all,
To start off Im talking linked issues and automation, so for the description below ISSUE-A will be 'fullfilled by' ISSUE-B, and therefore ISSUE-B 'is fullfilling' ISSUE-A.
I have an automation that is called when an issue is linked, it takes a field from ISSUE-B and updates a field in ISSUE-A with the field.
What I now want to do is create another automation that will clear that field when the issues are unlinked. However I cant see to get the unlink autoamtion to act on ISSUE-A, it always runs on ISSUE-B.
Here is what I have setup on this new automation, and feedback would be fantastic!
Thanks
Hi @Toby -- Welcome to the Atlassian Community!
Would you please post an image of the audit log details, showing an example when the rule does not work as expected?
Until we see that...
Consider that once the link is deleted, my understanding is the smart value {{destinationIssue}} no longer has meaning. Instead you could try using the changelog information to get at the previously linked issue, or invert the link type for the trigger.
Kind regards,
Bill
Thanks Bill, heres a changelog from running the automation just now.
I wanted to run on CRM-516 but it looks like it ran on CRM-625 instead despite me making the change on CRM-516.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Interesting as I would have thought that smart value would be empty with that trigger!
It appears you are using an advanced branch over {{destinationIssue}}. Please instead try selecting a branch type of:
Branch rule / related issues > Destination Issue
Even though the rule editor seems to indicate it only works for "Issue Linked" it appears to work for a delete also.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Bill, I swear when I first tried this destination issue was not availiable in the branch rule / related issues, thats why I went down the smart value route haha! The improtant thing is it is there now, and that has resolved it, its finally working, thank you for your help!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Awesome; I am glad to learn that helped!
The new UX is rolling out for the rule builder, and so I wonder if it "glitched" and wasn't visible for a bit. There is more dynamic content happening in the builder now, so I could see it changing the list of things, even though I have not observed that yet.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
yeh it wasn't this new UI when I setup the rule, so it could be that, infact, lets blame that, and then I don't have to admit that I might jsut have missed it...!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.