In previous version of this plugin, I was able to configure it to make a custom dropdown field and the Assignee field a required one. After I upgrade it to latest version, and for use with JIRA 5.1x, it is no longer the case. Specificially:
* For Assignee, if someone chooses 'Automatic" in this field, the field becomes not required. This is not the case in earlier version.
For a custom dropdown field, it is never a required field. So the "None" value can be selected.
Hi Gil!
You can set fields as required in workflows as vaidators too. I was wondering if you need other another option.
Gyuri
> For Assignee, if someone chooses 'Automatic" in this field, the field becomes not required. This is not the case in earlier version
I think it should be marked as filled if the selection is Automatic. That was probably a bug in earlier versions that I fixed.
> For a custom dropdown field, it is never a required field. So the "None" value can be selected
I won't be able to check this until later but I'm surprised because I think I have tests for this. Can you post some code...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jamie - there's no code on my end. Basically, I have a custom field with some dropdown value. Default is 'None' (system one). Our requirement is someone must choose a value other than None for certain status.
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.