Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,293,292
Community Members
 
Community Events
165
Community Groups

Why are my custom request types not appearing in the list of email request types I can choose from?

The only request type I can choose for my email requests in "Bug" but I want to use the less specific "General" request type and then assign it down to something more specific from there.

2 answers

1 accepted

3 votes
Answer accepted

@zachm Where are you not able to select the custom request types in the email request types could you please explain a little more about the issue so that I can help you on this.

Sure thing. I go to Project Settings > Email Requests and I click the three dots in the top right-hand corner, which brings up a drop-down and I select "Configure email request types". Each of my request emails are listed on the modal that appears, and each one has an associated option selector for choosing the request type to be associated with that email request.

The only request type available, however, is Bug. There are 2 email requests (connections?) on this project, and I want1 of them to be Bug and the other to be General, but neither option selector has an option for the General request type I created (Project settings > Request Types).

This is a classic service desk project with 4 users on it, if that makes any difference.

Ahhh I see I know why it might be happening, the reason you might have made more than one field mandatory on the request types which you created. To be able to link a request type with the email request only the Summary field can be mandatory if you make the other fields mandatory apart from Summary field they would appear on the "Not suitable for email" section below which means that you can still use them in the portal but not through email.

The reason is because if you have other fields apart from Summary marked mandatory the email would not be converted into a tickets in JSD, when a new email comes in the Subject of the email goes into the Summary and the Body of the email goes into the description and since Summary is a required field in Jira so just go into your request types and make make all the other fields in that request as not required and that shoudl solve you issue.

Hope that helps!!

A-ha! The only field I had listed on the request type was the summary and it was required, but if the email request turns the body into the description, it would not have a field to add that body to. All I needed was to add Description to the request type and it solved my problem. Thanks for helping!

Like # people like this

In my situation, I deleted the default email request Request Type, then later decided to re-create one.   When I created a new request, it only put the "Summary" field into the Visible Fields under Request Type > Request form, no "Description".  Upon reading this thread, I added "Description" to the Visible Fields, but still no luck.

To resolve, I added "Attachment" as well to Visible Fields under the Request Type > Request form, and it worked.  It makes sense to me that an inbound email request should (or must) have an "Attachment" field.

Like Mehrnaz likes this

Thanks @Walker White your solution saved my day!

This solved my problem as well. Thanks!

Suggest an answer

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

Jira Service Management Documentation Opportunities

Hello everyone, Hope everyone is safe! A few months ago we posted an article sharing all the new articles and documentation that we, the AMER Jira Service Management team created. As mentioned ...

158 views 0 4
Join discussion

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