The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

To make inbuilt select list (cascading) mandatory on both the selections

Sai Abhiram Chunduru (XFND36)
Contributor
June 29, 2022

Hello ,

There is a custom field built using the selection (cascading) which has two dropdowns (A & B).

A has three options

B has respective selections for A(1) , A(2) & A(3) . This custom field is being used in the request type forms over the customer portal and the field is made mandatory as well.

 

Unfortunately , sometimes the incident reporters are selecting only the first level dropdown which has options A(1) , A(2) & A(3) and they are able to submit the form without the selection of B dropdown/selection .

Is there a way to make the field mandatory in such a way that , both level 1  & level 2 dropdowns are must before submitting the incident.

Please suggest.

Thank you 

0 answers

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

TAGS
AUG Leaders

Atlassian Community Events