Clone Issue - avoid doubles

[Priyanka Agrawal]

Hi Community,

I have a project with workflow where when an issue is transitioned from status Build to Test, few automated tasks are created. But when a user realize that oh no the test has failed and i need to go back to status Build. So he transitions the issue back to Build and when from Build it is transitioned to Test the second time, those automated tasks are getting created again. So i would like to avoid these double creation of tasks.

Your second suggestion :"use the "Condition" script for the post function and skip running the post function when a linked issue already exists" sounds good to me.

Could you please help me with this?

Attaching screenshots of the Postfunctions for automated task creations.

[Petter Gonçalves]

Hello @Priyanka Agrawal

Thank you for reaching out.

Per your description, I understand that when you transition your issues from the status "Build" to "Test" and it's not the first time, you want the automation rules configured for that transition to not be triggered. Is that correct?

Can you please confirm if you are using Jira Cloud? Additionally, can you confirm where you collected the screenshots provided?

I ask this question because I'm not aware of the features referenced in the screenshot you posted, so I believe it must be related to some third-party app or Jira Server application.

Anyway, your goal can be achieved on Jira Cloud by using Jira Automation, configuring a label to be set when the issue is transitioned for the first time from "Build" to "Test". These would be steps:

1. Navigate to the Project > Project Settings > Automation
2. Create the Automation rule following the template below. P.S: I used different statuses in my test site:
   
   

Following the template above, the first time an issue is transitioned to "Test" will cause the label "Transitioned" to be added to the trigger issue and the automated tasks will be created. If the issue was already transitioned, the label will be identified and the automation will not trigger. 

P.S: You can use any other fields to verify if the issue was already transitioned and hide it from your issue edit screen, so the field can not be manually removed by anyone in your team.

Let us know if you have any questions.