How to avoid duplicating issues when running an upgraded automation?

Martin Hladik
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 4, 2025

Hello,

My team currently has automations set up for four different "impact categories,"  which then create a series of linked issues and sub tasks. Sometimes the scope of an issue changes, and we need to upgrade the impact category. Currently, we have to rerun automations for the new impact category, which duplicates several issues from the prior impact category while also creating the new issues needed for that updated category. How do I set up automations to only create the new tickets required for the upgraded impact category?

1 answer

0 votes
Lucas Knorr
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 4, 2025

Hi @Martin Hladik
you will have to add some if conditions to your automation rules to check, if the issue you are trying to create in this run, already exists.
For this to work, your if conditions will require an unique identifier to identify the already created issue. Maybe you can use the summary for that?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events