Ticket still creates when required field is empty

[Bridget Caci]

Hello!

I have a field set to required on my customer request form.  However, if I create a ticket and leave this required field empty, the ticket still creates.  I need the ticket to give the customer an error when they are completing the form and prevent the ticket from being created until the required field is completed.

The field is a custom field, Global context and is added to the project screens.  There is no post function/validator/condition on the workflow set to clear this field.  There are no automations on the project, at all.

The field is shared with other projects so I do not want to change the Field Configuration to required as it is not required on all the projects that use it.

This field is not used on all the customer request forms in this project.  But all the customer requests all use the same workflow, so I do not want to set a requirement on the Create transition.

I have set fields to required on the customer request form many times but this is the first time that Jira is not recognizing it.

Has anyone else experienced this?  Is there a resolution? I use JSM Data Center.

Thank you for your help!

[Florian Bonniec · Accepted solution]

Hi @Bridget Caci 

If you set the field required on the customer portal, it should be required. Not sure but does this field has a default value in the field context ?

Regards

[Bridget Caci]

Hi @Florian Bonniec 

No, this custom field does not have a default value.  The field is built as a Select List (single choice).

I'm completely stumped as to why I can still submit a customer request form even when my required field is empty.  I have another field on this same form marked as required.  I tested leaving it blank and was not able to create the form.  So somehow, this seems field specific.  But I've run out of ideas to troubleshoot.

Thank you for any help you can offer!

[Bridget Caci]

Apologies, @Florian Bonniec

I went through the custom field settings again and did see a default value.  Once I removed that, the required field is working as it should .

Thank you so much for your advice!

Really appreciate your help!

[Jennifer Maurer]

@Florian Bonniec I am having this exact same issue, however my custom date picker field does NOT have a default value. Any suggestions on what else might be causing my workflow condition to ignore this field requirement?