Advanced Conditional Operators in JSM Forms

[#1]

Hi Power Users!

We’re excited to share a sneak peek of our upcoming Advanced Conditional Logic feature for JSM Forms. Check out this short demo video to see early designs in action:

We’d love to hear your feedback!

• What do you like about the new logic capabilities?

• Are there any use cases or features you’d want us to include?

• Is anything missing or unclear in the demo?

Please reply to this post with your thoughts, or fill out this form.

Note: This is an early development demo; final functionality and behaviour may change.

Thank you for helping us shape the future of JSM Forms.

Best
Anshumaan

[Claude Eller]

Thank you for this. It's looking great.

I'd want the possibility to add "read-only" fields in JSM Forms. Is that something your team can add or implement soon? I have found very old feature request tickets for this as it seems to be highly requested but nothing has been done since.

Regards,
Claude

[David Todd]

This is incredibly useful for complex forms - nice one 👍. Previously we had to repeat sections if a question could apply based on the responses to more than 1 question above. 

[Daniel Santiago]

I would like to use JQL to hide/show Form fields/sections like it's possible with Playbooks. For example, show certain Form fields only to users within certain groups. Show a field to External Users group but hide from Internal Users group. Show a section if Request Type is X, hide if Request Type is not X.

Hiding fields in general (https://jira.atlassian.com/browse/FORMDC-60, https://jira.atlassian.com/browse/JSDCLOUD-10811) would be very useful.

[Todd Thomas]

This looks amazing and would be very helpful, @Anshumaan Bhartiya !

Would it be possible to show:

1. A visual indicator if logic is being used as a condition for a section? Like a flag on it or something that changes the section's appearance?

2. A short summary of the conditions used? I'm thinking something like Automations uses in the Components area.

If this is implemented without some visual indicators, it will be a big challenge to scan through a complex form and understand the logic used for each section without opening each one up one-by-one.

[Josh]

Hi @Anshumaan Bhartiya .

Our team has been anxiously awaiting this kind of functionality and it's exciting to see that you're actively working on it. Would you be open to having a call to discuss further? We have a bunch of use cases in mind at an enterprise level.

Our CSM, Philip Li, can get you in contact with us if you'd prefer not to post your contact info here.

[Matthew Challenger]

Looks great! Good job.

[Fernando Eugênio da Silva]

Awesome!!!

[Bill Goetz]

Love what I see so far! We use fields in our forms that are tied to Assets. Will this functionality be able to be used within the logic?

+1 to @Daniel Santiago suggestion of being able to have logic tied to a user's group or team.

[Tomislav Tobijas]

Nice one! Great to see some updates in this area 🙂

[Susan Waldrip]

We would use this capability extensively! Agree with @Todd Thomas on the visual indicator/separator so we can tell what's what for easier build and changes. And I'm assuming you'd still be able to provide the options for the fields via either a linked Jira field or adding options directly to the form, as it is now?

Thanks for continuing to focus on adding Forms capabilities, these are really useful!

[Harrison Ponce]

This has been a long time coming and we CAN'T WAIT to use these!!!!!

[Brown_ Kelly]

This additional conditional logic is a great enhancement!   One other thing that would be useful for us is to be able to do conditional logic based on a selected Asset's attribute, other than the Name one.    For instance, we have some Applications setup as Assets, and one of them attributes might be License Required.  It would be great to be able to do the conditional logic based on that particular attribute, so that we could prompt for a Quantity if that attribute is true.   

[Michael Fileti]

From the video it shows the "is equal to" operator but current forms use the "Is any of" operator where you can select multiple items from the dropdown options. I just want to make sure you'll still allow the multiple dropdown item selection functionality.

I also use Assets heavily, so the more functionality we can add with Attributes or AQL would be very nice.

But overall I'm very excited for this!!

[John Wilson]

This looks like what I need, so kudos. :-)

[Quang Kieu]

This is a really exciting news since we are adopting Forms widely now across our service projects. From the demo, it appears to me that conditions are still primarily based on select/dropdown fields with pre-defined options.

In our cases, we would expect the condition to be more dynamic when handling different field types: Text, email address, or even the cascading list field to enforce different business logics. 

I really look forward to trying this!!

[Khai Nguyen]

let's go

[Joerg]

Thank you. This is great!

One question not answered in the video as far as I saw: Will it allow conditions like "If field A IS EMPTY" or "If field b IS NOT EMPTY?

[Joseph Fagan]

This looks great--what is the planned release date?