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

Randomly receiving error configured request type has too many visible required fields

Muhammad Ramzan_Atlassian Certified Master_

My issue type for email creation have three fields only

Summary (mandatory )

Description (optional)

Attachment (optional)

I am receiving this error randomly and couldn't find the cause. No other error logs showing anything. Could you please help.

Error message:

Configured request type has too many visible required fields

Accepted answers

Muhammad Ramzan_Atlassian Certified Master_

The reason behind this error was weird. I was using a listener which was updating the issue type and that issue type have some mandatory fields.

I disabled that listener. But i am still surprised, it shouldn't impact the mail handler, as listener was being executed after issue is created and mail handler runs before issue creation

All comments

Sachin_q0v8o8

Hello @Muhammad Ramzan_Atlassian Certified Master_ , make sure your request type has only Summary and Description as required, visible fields. And other fields must be optional. You can make those other fields optional from your Projects --> Project --> Project settings --> Request types. --> Edit fields. See Receiving requests by email

Muhammad Ramzan_Atlassian Certified Master_

Thanks for your reply but i already have all fields as options as i described above. Also i am facing this error randomly , if there are any mandotry fields , no email request will be processed

Sachin_q0v8o8

Can you share a screenshot of the "fields" associated with your "request type"

Muhammad Ramzan_Atlassian Certified Master_

7-24-2020 3-49-13 AM.png

Here it is, as i said before its random error. If this is the case none of the request should be processed.

Muhammad Ramzan_Atlassian Certified Master_

The reason behind this error was weird. I was using a listener which was updating the issue type and that issue type have some mandatory fields.

I disabled that listener. But i am still surprised, it shouldn't impact the mail handler, as listener was being executed after issue is created and mail handler runs before issue creation

Welcome!

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

Quick Links

Find more posts tagged with

server

jira-service-desk

jira-service-desk-server