Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

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

Muhammad Ramzan(Atlassian Certified Master)
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 21, 2020

Hi

 

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

2 answers

1 accepted

0 votes
Answer accepted
Muhammad Ramzan(Atlassian Certified Master)
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 29, 2020

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 

0 votes
Sachin
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 21, 2020

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)
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 21, 2020

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
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 21, 2020

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

Muhammad Ramzan(Atlassian Certified Master)
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 23, 2020

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. 

Sachin
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 23, 2020

Thanks for the screenshot! Can you try making description field required and give it a try again.

desarrollo September 29, 2020

Hello @Muhammad Ramzan(Atlassian Certified Master)

Did you find the reason for this error?

 

Regards,

Muhammad Ramzan(Atlassian Certified Master)
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 29, 2020

@desarrollo 

 

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 

Like desarrollo likes this
desarrollo September 30, 2020

Hello @Muhammad Ramzan(Atlassian Certified Master)

Thank you so much for your help and quick response!!!

With your answer we were able to identify the problem and proceed to solve it.

 

Thanks again and best regards,

Muhammad Ramzan(Atlassian Certified Master)
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 30, 2020

@desarrollo , you are welcome, happy to see your problem is resolved too.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events