Field is required even if it is not required in the field configuration

[Wan Ahmad Mustaqim Bin Wan Azmi]

I have this one field called 'Actual Result'. In the field configuration, it is marked as optional but when I go to creating an issue with this field, it shows as required. Other projects with the same field configuration shows optional and it is working as intended. I have tried reindexing both project and Jira to no avail.

Any ideas to rectify this? It is supposed to be optional.

I have searched around but found one similar post like this but that one does not have any answer.

Appreciate all replies,

Mustaqim Azmi

[Victor Law · Accepted solution]

Hi @Wan Ahmad Mustaqim Bin Wan Azmi

There are a few configurations that could enable the field to be required:

• Workflow's Validator, as mentioned by @John Funk 
• ScriptRunner's Behaviours

Thank you.

[Wan Ahmad Mustaqim Bin Wan Azmi]

Hi Victor,

Thank you so much for the reply. I accepted your answer as the issue was the field was mapped inside Behaviours. Removing the field solved it.

[John Funk]

Hi Mustaqim,

Have you checked the workflow to see if there is something there on the Create transition that would make it Required? 

Also, can you share a screenshot of what happens if you try to save the issue when creating and the error message it gives?

[Wan Ahmad Mustaqim Bin Wan Azmi]

Hi John, 

Thanks for your reply. I have found the culprit that makes the field mandatory.The field was mapped inside Scriptrunner's Behaviour. Removing it from Behaviour solved the issue.