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; } } }

Automatically change issue type based on email "to" field

Phillip C

Hi,

(TLDR below)

Basically, I've got an email account connected to Jira that has multiple aliases on the mailbox and I want to be able to automatically change the issue type based on the email 'to' field.

Use case:

Emails that are sent to spamreporting@mydomain.com, will be changed from the default placement of service request TO spam reporting (a custom issue type i created)

FYI I already matched my source to destination workflow - so thats all good there.

After much investigating I finally found how to add logging, validate json and get my email "to" field. Wow! (im pretty new to this so give me a moment here).

However, now I've changed the rule from manually trigger to Issue Created - it doesnt trigger. So I've tested a few different triggers, but no luck either. I thought about a time condition, but I don't really want to put in a run every 10 seconds / 30 mins / 1 hour type of trigger either - thats just barbaric.

Any ideas on what trigger i need to put in OR if there is just a way simpler method that what im trying to achieve?

TL;DR - why is my compare statement only working by manually triggering the automation rule and not for Issue Created?

Accepted answers

Angélica Luz

Hello @Phillip C,

Thank you for reaching out to Atlassian Community!

Checking your use case, it seems that the email information is taking a while to be populated, that’s why when using the “Issue created” trigger is not working.

What I’m trying to say is that, when the issue is created, the field is yet not populated, so the automation runs when it’s still empty. Using Manual trigger works because it takes a while until you open the ticket and click to run the automation.

You can try adding an action called “Re-fetch issue data” before adding the condition to try to slow down a little bit the automation. I don’t have any email and aliases to test the same scenario as you, so please, take your time to test and let us know how it goes.

Screen Shot 2021-03-31 at 10.21.27.png

Kind regards,
Angélica

All comments

JD_sjez00

Hi @Phillip C

You mentioned the rule isn't triggering, is it not triggering at all or is the condition not being passed?

If the condition isn't being passed could you put a log action before the condition and just check your smart value (and make sure it's set). Hopefully I can help you more form there.

Another thing worth noting is you can't edit the issue type for Jira Service Management tickets. We have an open public ticket for this https://codebarrel.atlassian.net/browse/AUT-1750

You could clone the request and change the type, then close or delete the old ticket.

Thanks,

John

Angélica Luz

Hello @Phillip C,

Thank you for reaching out to Atlassian Community!

Checking your use case, it seems that the email information is taking a while to be populated, that’s why when using the “Issue created” trigger is not working.

Screen Shot 2021-03-31 at 10.21.27.png

Kind regards,
Angélica

Phillip C

Yes! This is exactly what i needed in the automation. I thought the field was still being updated and thus not triggering, excellent action to use! That resolved the issue, thanks you so much!

Phillip C

thanks for the reply John. The rule is triggering, just the condition wasn't matching. The reply from @Angélica Luz with the re-fetch action placed in my rule after the the 'issue created' trigger is perfect.

Hector Vazquez

Hi @Phillip C

How did you get the "to" email address? Once the issue is created, I only see the subject (summary), the reporter and the email body in the description.

I have a Jira project and 3 email handlers that create issues (tasks). I want to set a component (or update a custom field) based on the email address that receives the email.

Hope you can give some insights, thanks!

Greg Shub

would love to know this as well.

Hector Vazquez_orad16

Hi @Greg Shub,

Couldn't find a direct way to do it, so I created a "buffer" project for each email address where I receive the issues and "pre-process" them using automation (creating a new issue in the destination project setting component, team, etc.)

Phillip C

sorry guys but this field looks to be deprecated that I previously used to route incoming emails based on the TO address. I would hope there to be something, but it looks to be pretty lackluster from Jira at this point

If anyone else can determine how to find the "To" address in an email ingested to JSM please reply!!

Welcome!

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

Quick Links

Find more posts tagged with

cloud

automation

jira-service-management