Custom field configured as Optional but behaves as mandatory

[Jordan Janis]

I've seen various posts for this and the answer is, typically, the same.  In my case it doesn't appear to be a validator or field configuration.

I have a multi-line text field that is configured as Optional (in all Field Configurations, BTW) but when an issue is created/edited the field behaves as if it's set to Required.  The little read star appears and I can't save the issue if the field is empty.

I've checked and rechecked the field configuration and that the issue type and project I'm using are correctly configured and I cannot find the issue.  I went so far as to check EVERY field configuration in this Jira instance and, in all cases, this field is configured to Optional.

Any suggestions would be greatly appreciated.

[Trudy Claspill · Accepted solution]

Hello @Jordan Janis 

Do you have any third party plugins that might be causing this? For instance Adaptavist ScriptRunner has a Behaviors feature that can be used to make fields required.

[Jordan Janis]

We do have ScriptRunner... hadn't thought of that.  I will check that now.

[Jordan Janis]

Hi again.  Yeah, so it looks like there was a Behavior set up that made this field required at all times and was associated with two issue types across all projects.  Brilliant.

So, thanks for the heads up.  I would not have thought to look there because who would so such a thing?  Or am I missing something?  Is there any benefit at all to using a ScriptRunner behavior to make a field required as opposed to simply using the Field Configuration?

Thank you!

[Trudy Claspill]

That really depends on your environment, configuration needs, and Administration team. A field may be set as required in the Field Configuration, but if you have many Field Configurations and you want to ensure the field is required regardless of the other field configuration choices, then maybe a Behavior is more easily maintained.

If you think using a Behavior was the wrong choice, consult with the Administration team about instead changing all the Field Configurations to that requirement can be applied to only those two issue types across all projects. Note that might involve creating more Field Configurations to separate those two issue types from Field Configurations used by other issue types, and then updating the Field Configuration Schemes also.

[Jordan Janis]

Thanks again, Trudy.  Totally with you on this.

I will have to dig a little deeper but my suspicion is that either the Admin set up the behavior inadvertently - perhaps intending it to be for specific projects (there are other examples of Behaviors like this) or, more distressingly, it was done intentionally as a way of reinforcing the command-and-control type culture that I am actively fighting against.

Thanks for your help.

[Nic Brough -Adaptavist-]

What error message do you get when you try to create an issue with the field left blank?

[Jordan Janis]

Right below the field I see, "You must enter a value for this field" in red text.

[John Funk]

Hi Jordan,

Check the Create transition in the workflow for that issue type to see if there is a Validator there making the field required. 

Also, is this a Jira Service Management project?

[Jordan Janis]

Jira Software.  Definitely no validators.