Actions triggered by a button in a workflow are executed twice

[Jader Peixoto Volkmer]

Hi all, 

I need some help.

I created a button in a workflow to perform (From Any Status to Any Status).

I called the transition (button) Remever Acessos (Remove Acesses).

When the agent click on this button there are triggered some actions to open tickets in another project:

So, we are facing some problems related to this rule, tickets are created twice in the other project. The same ticket as the button was clicked twice. Thiniking to avoid this behavior I used a custom field Botão On/Off as a flag. This is, in the first time the user click the button and the action was performed, the Botão On/Off is set to ON. So, on the next time, the button has no effect.

On more information is that the email sent in the end of the flow was been sent only once, there is no duplicated email. So, I suggest there is something wrong with the Create Issue action.

Could you help?

Tks.

Jader

[John Funk]

Hi Jader - If you check the audit log for the rule, do you see if it executed twice or not? 

Is there another automation this is executing an auto transition that would trigger this rule? 

[Jader Peixoto Volkmer]

Hi John,

In the audit log is showing it is executed twice:

It looks like some strange that the tickets have the same ID in the audit log. But look the linked issues we can see different ticket IDs.

[Jader Peixoto Volkmer]

Hi Mikael,

thanks, it explain the duplicated tickets in audit log.

But the problem persists. I still have the creation of two tickets in each "Create Issue" command. And it only happens using the action button. I have the same actions in another point of the workflow and it works Ok.

Is there any relationship from where I am starting the action?

[John Funk]

So, I don't think you answered by other question. Is there another rule that executes that auto transitions the work item to this status? 

If not, is the box checked for the rule that says to allow it to execute from another rule? It is on the Rule Details page. 

[Jader Peixoto Volkmer]

Hi John,

Yes, the box is checked.

[John Funk]

Okay, asking again - does this fire because another automation rule moves the work item into the Remover Acessos status? Or does the user manually move it to that status? 

If manual, then I suggest you remove the check box as that might be what is causing it to fire twice. 

[Jader Peixoto Volkmer]

Hi John, make sense remove the check box. I did it and I will be waiting for the next execution of the workflow.

Regarding to the Remover Acessos, it is a transition not a status and this transition only exists in this specific workflow.

Thank you.

[John Funk]

Understood, but how is the transition getting executed? Manually or by automation rule? (You can auto transition work items with an automation rule). 

[Jader Peixoto Volkmer]

Hi John,

I used this procedure:

Add a looped transition to perform transition actions
in the Atlassian documentation:

https://support.atlassian.com/jira-cloud-administration/docs/create-workflow-transitions/  

So, then I create this flow that is executed in that transition. To make sure that the operation will be executed only in this transition I created a custom field called Nome Transição where I write the transition name (Remover Acessos) when the customer click on the button (bellow)