Restrict an automation from creating duplicates

[Javanshir Mustafayev _ HIT]

I have an automation rule that creates an issue under the epic during the epic transition.

The epic workflow allows us to move back and forth on this status, and each time it creates a duplicate of the issue under it which is not needed. 

How do I set up the automation rule to check if there is such an issue type and prevent creating a duplicate?

[Javanshir Mustafayev _ HIT · Accepted solution]

I've managed to build the logic on my side and after tests, it is working

[Davide Cascapera]

hi, javanshir can u share ur conditions for generating the issue?

maybe you can fix adding another condition in the if-else block, but to give u a better suggestion I need to see ur condiotns

thank you

[Javanshir Mustafayev _ HIT]

@Davide Cascapera 

I have no conditions now:

When the epic is transitioned to STATUS, then create an issue.

I would like to add a check if the same issue type is already present under this particular epic, then skip the creation of the issue of a particular type.

I'll add a screenshot of how my rule looks now below:

[Davide Cascapera]

u need to specify this event, or u can just try to target the next stage of ur workflow where the issue doesn't go back,or  u need to create another stage in the workflow for the issue creation

[Javanshir Mustafayev _ HIT]

@Davide Cascapera 

with all respect, the options you are providing do not fit into the business model of this flow.

the wf cannot be changed.

the automation needs a modification where it will allow to check if the epic already has an RND Modelling issue type under its children and skip creating a duplicate, if it isn't there then create one.

[Davide Cascapera]

add this if else condition u can  change the type (I used sub-task in this screen)

[Javanshir Mustafayev _ HIT]

@Davide Cascapera 

tried this using the config on the screenshot and the automation stopped creating the issue no matter if there is one or not

[Davide Cascapera]

I'm pretty sure that this happened because "t" in issue type should be capital 

[Javanshir Mustafayev _ HIT]

@Davide Cascapera no, this doesn't matter at all. try it yourself in any filter or advanced search it's not case sensitive for issuetype or issueType

[Davide Cascapera]

I try it in my test project and it works 

[Javanshir Mustafayev _ HIT]

@Davide Cascapera please try with a JQL where you specify the issue type like it is needed in my case. Your example works with subtasks, this doesn't work for my case.