Automation Jira receives 2 events when only listening to 1 specific event

[Hunter1428]

Hey all, first time posting :)

For some reason a status which Fires two Events, Jira Automation if listening for a specific event picks up other Fire Events.

A few of our statuses have 2 Fire Events.

1. Generic Event
2. Send Request Email (Used for our separate request mails, based on a condition)

Our "Request Mails Automation" is only looking for the "Send Request Email" Fire Event. Jira Automation Audit log does show 2 Event Fires of which the automation are a few milliseconds apart. (Aka within the same second)

This also leads to an error in the audit log for "Transition Issue".

"(Error marking step #312859 finished: root cause: Tried to update an entity that does not exist.)"

For some reason it also receives the "Generic Event" and we get duplicated actions.

What I have tried:

• Deleted the status and re added = No Change
• Deleted the Event and re added = No Change
• Deleted the Automation and re created = No Change
• Tried a Different Status = No Change
• Swapped the Generic Event for the Send Email = Works but we need the Generic Event
• Removed the Send Email and told Automation to Use Generic = Works bug too causes other automation to trigger to slow and a F5 is needed.

Any ideas on this?

[John Funk]

Hi Hunter - Welcome to the Atlassian Community!

Can you post some screenshots of your rule and the error message you are getting in the Audit Log?

Also, can you give an exact example of what you want the rule to do? 

[Hunter1428]

Hi John

Apologies on the long delay.

I created a demo automation / workflow to easily show you the issue I'm facing.

Maybe this is me not fully understanding something but it seems the Automation receives all events when using the "Issue transitioned" trigger. I also noticed the same thing if "Multiple Triggers = Generic Event"

I wanted to use the "Transition Trigger" to certain transitions as I thought it was independent from "Events". Because I didn't want to add another "Event" to all my statuses for a separate system to run along side.

My workaround has been unfortunately to create another "Event" and use that instead of the "Issue Transitioned" Trigger.

Hopefully this info helps you with the problem I am facing / faced.

[John Funk]

Yeah, that looks like the best solution based on what you have going on. Is it still working out for you? 

[Hunter1428]

It sure is. It also forced me to rethink on some other automated areas and rework them with "Events". Which has actually made all our automation more controllable and simpler!