Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

We asked Atlassian, “Does their next higher version of Ji...

  1. We asked Atlassian, “Does their next higher version of Jira SM provide for more email integration functionality?
    1. Atlassian said, “This is already exists. See the "Receiving requests by email" in this Link 
    2. Tommy: Go to that link. It says, “Set up a suitable request type with Summary and Description as required, visible fields. Any other fields must be optional.” 
    3. What does “any other fields must be optional” mean? It seems to imply that they can pick up other information from the email. This is important to investigate.

Please response tot he question number 3 above.

4 answers

1 accepted

3 votes
Answer accepted
Daniel Eads Atlassian Team Mar 31, 2021

Hi @Mua Ly ,

The other fields for the issue type must be optional, because the email channel can only process the Summary (populated from the email's subject line) and Description (populated from the email's body) fields. If other fields are required for the issue type, the email handler won't be able to create the issue, as it won't know what to put in those fields.

The only other fields you can affect directly via email are the Reporter and Participants, based on putting people in the To or CC fields of the email itself.

As @Foo Guan Sim mentioned, you'll need to use an app if you want to extend the email handling capabilities in Jira Service Management Cloud . You'd want to look at an app that has some way of delineating custom fields in the email body, or parsing out text to go into custom fields.

You could also consider using Jira's Automation to look through the body of the email (transformed into the Description field when the issue is created) and use regular expressions or pattern matching to find information and populate any custom fields you need filled out. The fields would still have to be optional or else issue creation would fail, but the Automation could save you some time in the long run if it's able to find the information you need in the email and put it in a custom field.


All that being said though, if you truly need some information provided during issue creation (if you're considering required fields), the safest methods to ensure that would be:

Both these methods allow you to control which fields someone needs to fill out when they're creating an issue.


Thank you.

@Mua Ly I think you're in the wrong section of Community mate. This is the best place to get answers to your questions: .

Just to save you some time, the answer you are looking for requires JEMH. See:

Daniel Eads Atlassian Team Mar 31, 2021

@Foo Guan Sim right on - I've moved this part of the thread from the original place it was posted to its own question in the Jira Service Management part of Community.

Like # people like this

Who can assist us with this question?

I do not know.  My experience is limited to Jira Software; I have no experience with Jira Service Manager.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

JSM Jira Automation: How to Send SLA Breached Notifications

Hi Everyone, In   this tutorial,  we will show you how you can monitor an SLA, and send notifications before or after the SLA has been breached.   SLA Threshold Trigger The SLA t...

626 views 5 12
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you