"Configured request type has too many visible required fields"- issue not getting resolved

[suganyam]

Hello,
In request type we have only "summary" field as required, also we checked in field configuration and work flow, there is no other required field configured. but still we received this error. 

[Rilwan Ahmed]

Hi @suganyam ,

Welcome to the community !!

Project admins can make fields required or not in the JSM project settings --> Request type --> Select work category --> click on required Request type.
Click on the field and you can check/uncheck "Required" 

Iif you are still having any issue, please share the error screenshot. 

[suganyam]

Hi @Rilwan Ahmed 

Thanks for your response!

yes we checked this request form, and we have only "summary" field as required field.

please find the error screenshot 

[Rilwan Ahmed]

Hi @suganyam ,

Sounds like someone has changed the customer request type which is mapped to your incoming mail. Please find out to which request type your mail is related to. Then check this request type for fields marked as required.

Actually only summary and description should be required.

Go to JSM project settings --> Request type .
Clcik on each work category and check which has the "USED BY EMAIL CHANNEL" tag in it. 

[suganyam]

Hi @Rilwan Ahmed 

Request type "Emailed request" has the "USED BY EMAIL CHANNEL" tag in it. Only summary  field is marked as required in it.

Please refer the attached video and help to resolve this issue.
https://slack-files.com/TCT5GMGLW-F04F4URCW9G-8b98d72a4a 

Thanks.

[Rilwan Ahmed]

Hi @suganyam ,

I am not getting what is the cause for this issue. Request you to raise a support ticket with Atlassian support here: https://support.atlassian.com/contact/ 

Workaround I can suggest is, Create a new Request type and give a name. Add only Summary, Description and Attachment fields to it. 

Now go to Project settings --> Email request, Click action button and click Configure email request types, select the new request type. Try sending an email and see if the issue exists.