How to stop repetition of automation rule in jira cloud

[Pantham Akhil]

Hello everyone I have implemented a automation rule which creates a checklist when an issue transitioned from on status to another it's working fine but the Problem is when a user is want to re transitioned the status it will creates another duplicate checklist how to prevent this problem. Please help me out ..

Thank you

[Vishwas · Accepted solution]

One possible solution would be to create a custom field, so when the ticket gets transitioned set that custom field to some value in the same rule of automation.

Add a condition in the rule before creating checklist to check if the custom field has that value in JQL( Example "Reopened" = No) then do the automation or else don't do. This would ideally avoid duplication.

Please check out this similar thread too https://community.atlassian.com/t5/Marketplace-Apps-Integrations/Automation-for-JIRA-how-to-stop-rule-repetition-for-the-same/qaq-p/1530996

Let me know in case of questions..

[Pantham Akhil]

Should I need to add a custom field which is a multi select field and need to add default value to that field or else can you please elaborate this one 

TIA

[Vishwas]

Multiselect is not required, just a select value is fine like yes or no kind of options.

So for the first time the transition happens, set the custom field value to yes in the same automation in another action.

Let me know in case of questions.

[Pantham Akhil]

Hi @Vishwas 

Still unable to configure can you please give me your email id or else can you msg me panthamakhil@gmail.com 

Thank you! 

[Vishwas]

Let me write the rule and send it

[Vishwas]

Hey @Pantham Akhil 

Automation rule is ready.

Before doing this i created a field called "Issue Transitioned ?" with Yes and No as dropdown values and added the field to edit screen of the project.

Try this and let me know in case of any issues.

Regards,

Vishwas

[Pantham Akhil]

Unable to find the custom field which I was set in the rule 

[Vishwas]

please check my rule. I haven't put the edit condition at the top. We need to put a JQL condition there. Then at last the edit action.

Also add the field created to the screen of the project.

[Padah JIRA]

meet.google.com/rai-mgnc-axp if you free can you please join this meeting once?

[Sukruth M S]

Hello @Pantham Akhil , you can  manually turn off/disable the automation after it is executed correctly as defined by you when you don't need.

Hope this helps you, @Pantham Akhil 

Thanks,

Sukruth M S

[Vishwas]

This doesn't make sense, disabling rule is fine ?. It entirely stops the running of automation, isn't it ?.

What if the checklist has to be created for other issues, stopping isn't a solution. As the whole purpose of automation written for creating checklist is defeated.

from the requirement @Pantham Akhil  is asking is there way to ignore the issues for which the automation rule has been executed at least once for them.

[Pantham Akhil]

Yeah @Vishwas  that's correct disabling rule doesn't make any sense actually I want prevent the duplicate creation of checklist when an user go back to previous status and doing the same transition the rule again creating a new checklist ...so I want to stop that duplication

[Vishwas]

Hey @Pantham Akhil 

Got your point.

Please send me the rule that's already running, let me see and suggest you.

Regards,

Vishwas

[Jack Hunter _HeroCoders_]

You need to set proper rule conditions, so it doesn't start when you don't need it. 

[Pantham Akhil]

[Pantham Akhil]

Here is the rule @Vishwas please check ...

[Pantham Akhil]

Unable to put an exact condition @Jack Hunter _HeroCoders_  can you please help me in this

[Jack Hunter _HeroCoders_]

Please show also the edit issue details on the screenshot.

[Guaraci Nakamura]

@Pantham Akhil your automation is very close to the one i created, however ALL issues are triggered, consuming the execution limit. How do you solved this point?