automate specific assigns if from specific email domain

[Tim Gesner]

I'm trying to get jira to auto-assign tickets that come in from a specific domain (anybody@domainname.com) or just (@domainname.com) to a specific individual, and not assign it by round robin.

[Trudy Claspill]

Hello @Tim Gesner 

Welcome to the Atlassian community.

Does this concern Jira or Jira Service Management?

Does this concern the Cloud or Data Center version of the app?

Have you started constructing this rule yet? If so, show us what you have so far, and let us know where you are stuck.

This post asks about how to check if the Reporter of an item is in a specific domain, and the answer shows how to do that. That condition can be used to then proceed with setting the Assignee for the item. Let us know if this helps or if you have additional questions.

Trigger automation based of reporters domain 

[Tim Gesner]

When: Work item created

If: Compare two values {{issue.reporter.emailAddress}}

contains

@domain.com

Then: Assign the work item to
Specific user

And: Edit work Item fields
priority

This just doesn't do anything & I'm not sure -why - I've tried getting ROVO to help create it but it lists "Ends with" which I don't have as an option.  I've also tried doing the same thing with entire email addresses and that doesn't seem to work either (adding multiple email addresses into Compare

[Tim Gesner]

[Trudy Claspill]

Thank you for that additional information.

Can you provide a screen image of the Condition you have created?

For the Value in the condition have you literally entered @domain.com or did you enter the domain you expect to find in the Reporter's email address?

Can you add a Log action before the Condition, and in that Log action enter the smart value you are using in your comparison - {{issue.reporter.emailAddress}}

Make sure that you copy the smart value from the Condition into the Log action to ensure you are referencing exactly the same smart value in both places.

Execute the rule again and review what is shown in the rule execution log file. Does it show the correct email address for the Reporter?

[Bill Sheboy]

Hi @Tim Gesner -- Welcome to the Atlassian Community!

One possible cause of the symptom you observe is the known, racetrack timing defect with the Work Item Created trigger.  That is, the work item data is not consistently available when the rule starts.

The mitigations for that are:

• Immediately after the trigger, add a Re-fetch Work Item Data action.  This will slow the rule slightly, reloading the data before the steps proceed.
• Although not used in your rule, never use the new feature to add conditions directly to this trigger.  As the data could be incomplete, the condition results will be unreliable.  Instead, add individual conditions after the above noted re-fetch action.

Kind regards,
Bill

[Tim Gesner]

@Trudy Claspill & @Bill Sheboy - I've added the re-fetch & the log, I'll post the results as soon as I can.

[Tim Gesner]

Success!  I think it was the "Re-fetch" that worked, because my logs showed unsuccessful before I added that - good info to know!  Thank you both!