While opening a JSM ticket, we face a gap when our users switch from one field option to another.

CONTEXT: Conditioned fields only show their options when matched a proper criteria (choose this, then the next field offers those options).
GAP: When they want, they are able to go back to the father field and change it but the previous son field remais its previous chosen option, ending in a irregular fields options combination.
INCIDENT: Eventhough this should not come to be, they are able to open a ticket in this irregular way. 

Could you help us solving this, please?

(obs: I tried opening an Atlassian Bug and Support tickets, but the interface lacked the button or field obligatory to create those kinds of ticket, so I've opened it as a Suggestion)