I created an automation rule to update the Slack user ID in Jira tickets as follows:
Is there a way to set a condition so that the automation only runs when there is a value match in the lookup table? In other words, if there's no match, it shouldn't change to "none."
Note: I’d like to optimize this rule to reduce my automation usage count.
Based on the rule image you show, there are several ways to do this:
I hypothesize there is another rule which uses the Feedback Slack User ID field to send messages. Please consider: what should happen when the Assignee is not found for sending that feedback? For example:
Kind regards,
Bill
@Bill Sheboy It seems the first way meets my need. However the automation isn't working for both scenarios: match and no match (between 'assignee ID' and 'slack user ID'). I've attached the condition I've added. Could you please advise?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
First, your rule steps are out of order: the condition should be after the table is created!
Next, there is a typo in your condition you highlighted: there is an "a" before the issue smart value.
Finally, I believe you want the condition to be "not equals" empty, thus the rule continues to run if a value is found with the get() call.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi there,
May I suggest adding an IF/ELSE condition after the create lookup table action. Pair that with a smart values condition in the "If matches" branch and I think that may get you what you're looking for.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Chris Rainey Thank you for your suggestion! Could you please provide more specific guidance on how to implement the IF/ELSE condition after the create lookup table action?
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.