I have a Transition which I wish to make conditional the login person being in a particular project role and (amongst other things) a specified radio-button field is not set to 'None'. I have set the Condition to != None but when the radio-button is set to None the Transition is visible. It seems the None value allows a Condition to be bypassed.
Is 'None' an option? Usually, when you select 'None', it means no options are set (unless you add an option called 'None', which is not recommended).
Check for empty value instead of checking for 'None' and see if that makes a difference.
I posed the original question. The option 'None' is a JIRA standard and, it would appear, cannot be removed. The setting of conditions where only the 'all of' OR the 'any of' selections are available makes the design more difficult (but not impossible). The un-removable 'None' option, however, appears to operate by a third set of rules and that is what makes this problem difficult. The potential of the 'Object ID' option is not well explained in the documentation.
I was referring to that in my answer. 'None' is not an option, it just says no options are selected. (I have seen admins creating a 'None' option themselves but that adds more issues). In this case, you should be checking for empty (null) value.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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