Set radio buttom custom field to mandatory

[Vishal]

Hello Guys,

I have three custom fields all are of radio button type, the second & third field is visible based on the selection of values in the first field. Till then second & third custom field is set to hidden & not required  using behaviour.

Once second or third field is visible, I need to set them to mandatory, however even after setting them to required, they are not actually mandatory field & we can create a ticket without selecting any option.

Is this some sort of bug in radio button type custom field or something ? Do let me know if anyone has encounter something like this & if there is any solution to it.

Note : I am using a java code to remove the 'none' options from all custom fields.

[Vishal · Accepted solution]

Just for the information if at all someone faces this issue, it seems like a bug if you use cascading radio button, second radio button field doesn't really become mandatory even if you set it as required in initializer. So to mitigate this, use field validator function in workflow instead. This will work as a workaround.

[Gustavo Félix]

Hi @Vishal
Are you using any automation plugin ?

[Vishal]

Hello @Gustavo Félix 

Yes, we are using automation for jira plugin.

Vishal

[Gustavo Félix]

I was going to suggest a transition validator , but I dont think that is included in automation for jira.
Here is a reference: 

https://community.atlassian.com/t5/Marketplace-Apps-Integrations/How-to-use-Automation-for-Jira-to-require-fields-before/qaq-p/1274783#:~:text=You%20need%20to%20use%20a,included%20in%20Automation%20for%20Jira.&text=Hi%20Clarissa%2C,the%20transition%20within%20the%20workflow.