You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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?
Here is a print screen of the field and the new defaulted value. It used to say "None"
Should look like this...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.