You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.
View groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
Scenario:
An issue can have 1 to many linked issues of type "Bronze Automated" (In link: "Automated in Bronze", out link: "Bronze Automated"). When an issue of that type is linked, the "Running in Bronze" field is populated it "Yes" (I have this working). What I'm struggling to get working is when "Bronze Automated" linked issues are removed, I want to change the "Running in Bronze" field to "No" only if there are no other "Bronze Automated" issue links. Currently, it'll update if any "Bronze Automated" linked issues are removed.
Here's a screenshot of the Automator rule:
I have tried both "Bronze Automated" and "Automated in Bronze" for the linked issue type in the "If" condition.
I just tried your scenario, using Blocks, and it worked for me. Have you tried to include both directions of the link in the If condition, in and outbound?
Best regards,
Bill
Hi @Bill Sheboy ,
I did just give that a try and the field still gets changed even though there is another "Automated in Bronze" linked issue.
I appreciate the suggestion!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hmmm... I wonder if there is something else happening.
Have you looked at the audit log for the rule and the history for the impacted issue to see if something you do not expect is occuring?
Have you confirmed there are no extra link types with similar names? (e.g. extra white-space)
Another brute-force way to try this is to join the links names into a string...
{{#issue.issuelinks}}{{type.name}}{{^last}}, {{/}}{{/}}
and then check for the word "Bronze" being absent to clear the setting. Seems overkill when the links should work with those dedicated automation tests and actions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
After a few errors of troubleshooting and trial and error, I ended up using your brute force method which worked. I'm really at a loss as to why I couldn't get the built-in functionality to work. I'll chalk it up to my lack of experience in Jira. Thank you @Bill Sheboy for the assistance.
For anyone that comes across this question in the future, I added the following rule in place of the "Linked Issues not present" step in my original image:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, Richard. I am glad that you got this to work, and I wonder if you have uncovered some edge case. If so, please consider submitting a defect to Atlassian to learn why the built-in test didn't work for you on the links. Thanks!
__Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.