I am using Jira version 7.2.6 - i have tried making the fields 'required' on the customer field configuration but that doesnt work.
Community moderators have prevented the ability to post new answers.
Was this ever resolved? I'm on version 7.3.1 and also can't hide the None option in the radio buttons via the configuration. I've rest the configuration to Required, made the default option Yes, and I still see None on the screen. I re-indexed and still no luck. I can't remove the option from the entire system because none is an option in other custom fields. Am I missing something?
In the end I succeeded using SIL as follows:
1. Instant hook on the issue type
2. Instant action as follows:
if(argv["screen"] == "create") {
if (argv["issueType"] == "xxxx") {
lfRestrictSelectOptions("customfield_xxxx", {"None"});
But I understand that the more code I put behind the scenes, the slower things will run so I'd like to do this in the configuration if possible.
You have to specify a default value for that field. You can do this under Customfields -> Configure -> Edit Default Value
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It's default and mandatory - have you done both? (Both are at an issue level too, not project)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have just tried that too and its still there. When you say issue level do you mean the custom field is assigned to an issue type?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, but also the configuration - you can give an issue type a "field configuration" that differes from other issue types in the same project (and, of course, across different projects).
When I mess up fields, 75% of the time it's because I have associated the wrong field configuration, and 24% of the time, I've got the context wrong.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have just checked and i have already assigned a field configuration for that issue type. I have also assigned the custom field to the same issue type and i have set a default value & made the field mandatory.......AND its still there :(
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The default is assigned at the custom field definition level in the context, if you have different ones by project or issue type.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be missing something in the configuration.
I've just created a new radio button field with three options, and made it mandatory in the field configuration (for all issue types in the project).
None is no longer an option when creating a new issue.
One other thought though - could someone have added "none" as an option in the list of options for the field?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
JIRA 7.4 for that test, but I've also just tried it on 7.2, 6.4 and 5.2 to make sure my memory of the behaviour is correct.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.