Removed required custom field but still required by API

[Jeremy Wright]

We use Jira API to raise tickets

API working with following fields:

 - Reporter

 - Description

 - Custom field x 2

A custom field was mistakenly set to required, API then failed. 

Custom field was then set back to optional but the API continues to fail

Any ideas?

[Phill Fox · Accepted solution]

Hi @Jeremy Wright 

Can you provide the error message that the API responds with when it fails to make sure that the failure is definitely related to the custom field and the mandatory/optional setting. 

Have you checked that the custom fields are on the create screen for the issue? As there absence can cause unexpected hiccups with the API. 

This may also be completely off the point but have you checked that the credentials used to access the API have not expired? 

Have you checked your values for the API using a tool such as https://insomnia.rest/ to check that it is not a connection failure?

Hope this helps us to collectively progress your issue. 

Phill

[Jeremy Wright]

Thanks Phil, appreciate your quick response. 

It was on the Request Form for the Request Types. Making a custom field required puts it as a required field on the form but making it optional (in the custom field list) does not take it off the request form. 

Trick for young players!