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?

Hi everyone - a quick note to say that we have tentatively added this to our roadmap in the next 6-12 months. While we don't have exact dates yet, we understand its importance and will keep you updated on our progress.

Thanks,

Sam

JSM Principal Product Manager

Hello,

It would be great think to implement. We have some blockers in one project and must find some workaround.

It would be very useful to have AND/OR operators for forms and it also would be useful to be able to check if a text field is empty or not.

It would be very useful to have AND/OR operators for forms.

Current functionality is very limited.

It is quite common for ITSM to prioritze tickets by impact and urgency. This allows the user to get an idea of the response time his ticket will have before submitting it. Currently we resolved this issue with a table,, but it is quite difficult to read it.

We need to  automatically  show the time of first response and to resolution according to the selection of urgency and impact

All these ideas would help forms be more used. With current features there are a lot of limitations.

OR operator is not supported.

AND operator can be used (partially) with nested sections.

We have two use cases that we cannot achieve with the current design:

1. Show/hide a section depending on the Atlassian Group that the requester belongs to.
   • the workaround for this is to ask the user which group you belong to (and set the condition accordingly) and trust users to select the right group
2. Show/hide a section depending on multiple independent conditions
   • workaround for this is duplicate fields relevant to non-primary conditions with a downside that duplicated fields cannot be linked with one Jira field (refer to Peter Preston's comment in this community post)

It would also be great if the conditional could check against number fields.

e.g. if value of field "estimated cost"

=0 then X

>0 AND ≤1000 then Y

>1000 then Z

Also allow regex match for text fields in conditions