I've got an automation set up that flags tickets when they've become blocked by another ticket. I want to set up an automation that unflags them when they've been put in a certain status.
I'm using different projects and want them to behave different. I want to set up 2 automations or have the effect thereof.
1) When the blocking and blocked by ticket are in the same project I want to unflag them when the blocking ticket has come in the status: "In Review".
2) When the blocking and blocked by ticket are in different projects I want to unflag them when they're in the status: "Resolved"
I'm having some problems with setting it up. I can't find a way to do the same or different project bit. How can I fix that?
Hi @Max Boerma
Please try an advanced compare condition and test with the smart value {{issue.project}}
https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/
Kind regards,
Bill
Hi @Bill Sheboy
Thanks for the help! I've been trying to get it to work but can't figure out how (I don't know what the second value should be.
I think I'm doing it wrong with the second value right? I've tried {{destinationissue.project}}. I can't find a way to compare it to the project of the linked issue.
Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, Max. Thanks for adding more information!
First thing: I recommend implementing this one-rule, and one-status at a time. Once you have it working you can decided if/how the rules can be merged.
Next, some follow-up questions:
If you have anything other than one-to-one blocking links, you could get into a situation where it is not possible to determine "flagged" or "not flagged".
If you only have one-to-one links, rather than using branches on links you could use a branch on JQL to set a created variable based on the linked-issues information, and then use that to decide about flagging. The JQL to get at the linked issue would be:
issue IN linkedIssues({{triggerIssue.key}}, "blocks")
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.