nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

automation triggers

Tom Meyer_zfhsk9

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.

Accepted answers

Bill Sheboy

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

All comments

Bill Sheboy

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_zfhsk9

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.

2020-08-25 13_29_37-Project automation - PEAK6 Jira.png

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.

Screen Shot 2020-08-25 at 11.41.10 AM.png

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

Tom Meyer_zfhsk9

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.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

automation

trigger