Setting up automated workflows can significantly improve efficiency, but it’s crucial to ensure they function as intended. This article addresses a common issue encountered when configuring sequential automations within a ticketing system, offering a clear solution to a specific scenario.
A user requested an automation that would automatically mark tickets as “Done” when created by a specific reporter and send Slack notifications for tickets remaining in the “New” status. However, the initial rule was incorrectly configured, continuing to trigger Slack alerts even after tickets were transitioned to “Done.” The root cause was a condition within the rule that excluded all issues not matching the reporter’s email address, effectively halting the automation process.
The system evaluates each issue upon creation. If the reporter’s email is present in the defined list, the issue transitions to “Done.” Conversely, if the reporter is not listed, the rule terminates without further action. To resolve this, an IF/ELSE condition should be implemented. This allows for the definition of actions to be taken when the user is not in the specified list, ensuring the desired behavior. Additionally, exploring the use of a Re-Fetch action within the rule could provide an alternative approach to achieving the desired outcome.
Ultimately, careful rule design and consideration of conditional logic are essential for successful automation. By implementing an IF/ELSE statement or exploring actions like Re-Fetch, you can ensure your automations accurately reflect your intended workflow and avoid unintended consequences.
Source: https://community.atlassian.com/forums/Jira-questions/Set-up-sequential-Automations/qaq-p/3057872