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

Example email for email-to-case

Akash Sharma_pdnubt

I am looking for an example email to enable email-to-case.

I have this email (epc@clearblade.atlassian.com - left of pic) and Request Type (right of pic) created:

Screenshot from 2025-02-04 14-31-12.png

The incoming emails will be sent by a bot in a different ticketing system. Our partner is able to configure the bot to format the sent email in any way we define, but it can only send emails (not HTTP calls etc.).

I just need a simple example email showing how one of these fields (e.g. 'Components') should be inserted in the email body in order to be parsed out successfully by JIRA to create an issue.

Accepted answers

Trudy Claspill

Hello @Akash Sharma

The email processor for JSM cannot parse the email as it is received to put the data into different fields when the issue is created. It will put the Subject of the email into the Summary field, and the Content of the email into the Description field.

If you want the Content of the email parsed and used to populate other fields in the issue/request then you will have to do that after the issue creation is completed. You could use an Automation rule with the Issue Created trigger to handle that process.

If you can dictate the format of the email content then I recommend that you tell them to put at the end of the email:

keyword: component-name

You would need to make sure you specified a value for keyword that is unlikely to be used anywhere else in the email content.

In the Automation rule you could extract the component-name from the Description using the substringAfter() function:

And use that to set the value of the Components field.

If the content needs to be able to specify multiple Component values, I would recommend a comma separate list. You could iterate over the comma separated list with a For Smart Value branch, using an Edit Issues action to add each value to the Components field.

Screenshot 2025-02-04 at 2.57.57 PM.png

All comments

Trudy Claspill

Hello @Akash Sharma

If you can dictate the format of the email content then I recommend that you tell them to put at the end of the email:

keyword: component-name

You would need to make sure you specified a value for keyword that is unlikely to be used anywhere else in the email content.

In the Automation rule you could extract the component-name from the Description using the substringAfter() function:

And use that to set the value of the Components field.

Screenshot 2025-02-04 at 2.57.57 PM.png

Bill Sheboy

Hi @Akash Sharma

Adding to Trudy's suggestions...

If you expect multiple Component values and want to add them to one issue, rather than using an advanced branch with several issue edits, I recommend adding them all at once using a single edit with JSON. This will reduce the risk of errors / update collisions and improve the performance of the automation rule.

Please look here to learn more about that technique:

Kind regards,
Bill

Akash Sharma_pdnubt

Thanks a lot @Trudy P Claspill and @Bill Sheboy! Much appreciated!

Akash Sharma_pdnubt

OK, I thought the rest would be easy but it is not. I am actually starting with a very simple single string. So in the incoming email body we would have this:

SystemKey: someString

So the keyword is SystemKey and the value is someString (with preceding whitespace removed).

I believe I'm able to use the substringAfter properly. But I am unable to set the value to a field called System Key. But that field always appears blank even though the email body clearly has the content.

I am trying to use this rule. What am I doing wrong?

Screenshot from 2025-02-04 16-39-16.png

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud