We also experience limitations because of form conditions! We appreciate an increase in possibilities as well.

This would be very useful!

This would be very useful - upvoted

This would be a game changer - 96677a1d9b4c are there any updates on timelines for this?

Whilst it's great to be able to add conditional sections, one after the other, so that multiple field values can be checked, these are all chained together as AND conditions.

The If, then, else logic would allow for 'OR' conditions to be evaluated.

Example: There are several dropdown fields with an 'Other' option. If any of these fields is selected then reveal a section called 'Other' to collect more details. 

Hi sharos.pillai - 

We have this same need for JSM. Here's what we do:

• Include all the fields we need in the screen definition(s). 
• In the Request type configuration: 
  • Only add the initial fields onto the "Request form" or the "Attached form" – the fields needed for issue creation.
  • Add the fields that were "hidden" (not added) to the "Issue view" (2nd tab in the Request type configuration page).
• That allows us to have a limited set of fields visible to the customer, but all the fields available to the agent.

If that was not useful, sorry! But hopefully that helps.

An option to hide a field while creating an issue and the field is visible while issue in different status.

We desperately need this.

We have been wanting to really build out our request forms using Forms but with the current options available it's just not good enough.

Don't get me wrong though, it is miles better than the vanilla request forms, but it still needs more work.
It needs this to go from "Well that's nice" to being "really good".

96677a1d9b4c is this still being looked at, or has it been dropped?

Hi 96677a1d9b4c, any update on whether this will land on the roadmap soon?