automation triggers

[Tom Meyer]

I have an automation that assigns the epic, story points, sprint and assignee when a ticket is created in my project. We also have an email handler that auto creates tickets when an email is sent to particular address. 

Is there a way to *only* have the trigger fire if it comes from the email handler (the vast majority of the tickets) and not from a person creating it manually within Jira ? The problem is that if a person creates a ticket and they already know what epic/sprint/story points/assignee they want to use, the automation overwrites those values and that's not ideal. 

None of the existing triggers seem to be relevant.

[Bill Sheboy · Accepted solution]

Hi @Tom Meyer  -- Welcome to the Atlassian Community!

As I recall, you needed to identify a JIRA user for email-generated issues.  Is that correct?

If so, could you add a user condition to your rule that limits edits to only those issues created by this email-generated source user?

Best regards,

Bill

[Tom Meyer]

well .. yeah. that's exactly what I am trying to do but I don't see any trigger that is based on who/what user generates the ticket. the trigger as of now is just  the default 'Issue created'. Perhaps I'm just being thick.

[Mikael Sandberg]

The user condition that @Bill Sheboy is referring to is added after you select the trigger. Once you selected the trigger you can add condition, action and branch rule/related issue components to your rule.

[Bill Sheboy]

Yup, what @Mikael Sandberg said...

• Trigger: issue created
• Action: re-fetch (for safety to handle race condition errors and un-populated fields in the issue)
• Condition: user condition to match reporter to the email-generated user
• Action: edits for your fields...

__Bill

[Bill Sheboy]

Tom, you note that reporter will not work.  Is there any other information in the issues that is unique to items created by the email-generated ones?

If not, could you update the handler to somehow make them distinct, and so identifiable by the rule?

The other approach is to flip this problem around:

• When an issue is created...
• Check if any of the fields you plan to set are already populated; if so, bail out
• Else, set the field values.

Best regards,

Bill

[Tom Meyer]

We figured it out by having the email handler use a new issue type that it and only it will use instead of just 'task' and then have the automation only act on that new issue type.

[Tom Meyer]

Reporter unfortunately is set to the person sending the email so that won't work ... e.g. if I send an email to 'jiraticket', the reporter is myself and not 'jiraticket'.

None of the other fields show anything indicating that the ticket is generated by the email handler.