All, I am at my wits end with this and could use some help solving what should be a simple, solvable problem. I have several custom fields that I need to remove the None option from (this is radio buttons or single-value select lists). I have followed the numerous guides that say to:
This has no effect. So, I went and bulk-changed existing issues which did not have a value set to one of the valid options. Still no effect. Do I need to change the context of the custom field to be scoped to this particular project? Or what else can I look at to determine why this is still showing the way it is? Do I need a JIRA restart? I would think not.
To further cause frustration, I followed the same steps as above like 2-3 weeks ago to successfully remove the None option. However, right now it is not working.
As a note, I am using JIRA Software 7.1.7.
If you don't have different contexts for the field then you should only need to set it to required. However, I believe that only works if you are requiring it in the field configuration, not during a transition. And re-indexing never hurts, just in case
Yep, I have been re-indexing regularly. We are still in a small deployment so it is only about 30s per shot. Can you clarify what you mean in the second sentence with regard to requiring it in the field configuration? To try to answer, I simply created the field, then added it to a screen, and the screen is required for Edit, Create, View, and Default operations.
Hey admins! I’m Dave, Principal Product Manager here at Atlassian working on our cloud platform and security products. Cloud security is a moving target. As you adopt more products, employees consta...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs