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

Email request - cannot change to new issuetype

Simon Sahli

Hey community,

I have created a new issuetype and I want to change that request via mail are connected to this new issuetype.
To achieve that I am in the Project settings in "Email request" and entering the "configure email request type" menu. There I want to select my new issue type, but it does not show up, so therefore I cannot select it.

What could be some reason that the new issuetype does not show up as an option here?

I have created the issuetypes some days ago, so it cannot be that this menu is not up to date.
Thank you very much in advance!

Kind regards,
Simon

Accepted answers

Dirk Ronsmans

Hey @Simon Sahli and welcome to the community!

You mention you created a new issue type, did you also create a new Request Type?

By default you map a Request type to the email handler and that Request type is linked to an issue type.

Be sure that the issue type only has mandatory fields for Summary and Description or that too will cause an issue (if there are more, since the mail handler can only map those 2 fields)

All comments

Dirk Ronsmans

Hey @Simon Sahli and welcome to the community!

You mention you created a new issue type, did you also create a new Request Type?

By default you map a Request type to the email handler and that Request type is linked to an issue type.

Be sure that the issue type only has mandatory fields for Summary and Description or that too will cause an issue (if there are more, since the mail handler can only map those 2 fields)

Simon Sahli

Hey @Dirk Ronsmans , thank you very much!

I have created the request type with it.

Jep, then that is the source why the new request type is not displayed, since we have now more fields than only the summary and the description.

So I guess then this means we need to create a default request type with only the summary and description field and then we get a new issue we reassign it manually to the right issuetype? Or what would you say is best practice here?

Dirk Ronsmans

@Simon Sahli ,

well it can have more fields but not more mandatory fields, otherwies Jira has no idea what to do with it as they cannot be mapped and it cannot be created.

Simon Sahli

I see, the thing is we want that our customers use these fields, like a severity field for example, to give us some more information and if we make them non-mandatory, then we are afraid that they won´t fill them in.
As a quick solution, I made all fields except the two mentioned ones non-mandatory.

Anyhow, I think the question is also if it really makes much sense that we allow customers to create issues via mail or we rather force them to use the portal...
This is however not my decision, but I can now explain the situation better and we will need to make a decision.

Thanks again @Dirk Ronsmans , that was fast and really helpful. If this always going to be like that in this community, then going to work with the Atlassian products will be amazing.

Thomson Jones

It was very well authored and easy to understand. Unlike additional blogs I have read which are really not that good.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

request

jira-service-management-cloud

jira-service-management