The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

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

Required Select field not defaulting to NULL

Michelle Gronwold
Contributor
April 24, 2023

We have recently upgraded to Jira v9.4.5. After upgrading my users have noticed that our single select custom fields are not defaulting to NULL. It is defaulting to the first option in the dropdown list.

Example, I have a custom field called Benefit Type that is set as a required field. The first option in this field is "Anesthesia". Prior to the upgrade the field would default to NULL and the user would have to select an option from the dropdown list before creating an issue. Now the field defaults to "Anesthesia" and if the user doesn't change it, the issue will be created with this option selected.

Also, Benefit Type is a Dynamic Select Field using the Dynamic Forms for Jira app. Get started - Dynamic Forms for Jira (deviniti.com)

Has anyone else seen this issue?

 

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Michelle Gronwold
Contributor
April 24, 2023

Here is a print screen of the field and the new defaulted value. It used to say "None"

Capture.PNG

Should look like this...

Capture2.PNG