I would like to set up an automation where:
1) The system recognizes the reporter and auto sets the tickets to Status=Done based on the reporter email address.
2) I then would like the system to send out a slack notification for tickets that are still in status "New"
I set up the rule below but the system still sends slack alerts on tickets where status = Done.
Hi, @Olivia Nedved
Welcome to Atlassian Community!
Your rule won't work as intended because the first condition excludes all issues created by users not in your list — and when that happens, the rule simply stops.
Let me explain how it currently works:
To achieve your goal, you should use an IF/ELSE condition instead. This way, you can define what should happen if the user is or isn’t in the list.
Hi @Evgenii
I mentioned this as well, not as elaborate though.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Great point — it’s probably the most obvious solution, which is why it came up quickly.
But we're here to help, not to keep score of who replied first. Especially when the answers are just a minute apart! 😊
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Olivia Nedved !
Try to use Re-Fetch action in your rule
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Welcome to the community.
Use and IF/ELSE condition in the rule.
On the IF use the if reporter in ... then transition to done and in the ELSE the conditions based on issue type and status and sent the slack message.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Olivia Nedved
Welcome to the Atlassian community.
After updating a item in a rule, use the Re-fetch issue data action to get a new copy of the updated item. Otherwise the rule may be working of the information in its cache for the item.
https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Re-fetch-issue-data
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Evgenii 's answer is better than mine because of their correct assessment of the impact of the first condition looking at the Reporter of the issue. My answer did not consider that.
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.