Why is a custom drop down field (linked Jira field) not showing all options a customer field?

[Amy Goss]

My organization is using the JSM "Report a maintenance issue" form for our customers (aka staff) to report/request maintenance. For a better UEX, the form has been built using conditional fields to easily navigate to the campus/area/room since we operate multiple facilities. The conditional fields are linked to custom fields that are filtered object assets.

Not all options will load for the customer. The workaround (that doesn't always work) is to select the last option, then expand the dropdown again so the remaining options appear. This is annoying and not user-friendly.

Is this a bug, or is there a limitation to the conditional field? 

The example below is for a campus with 116 rooms (objects) associated with the "Main Building." Only 50 of these rooms will load when the last conditional dropdown is expanded. In this case, the workaround mentioned above does not work. This problem is not isolated to only this form field.

A screenshot of the custom field configuration.

TL;DR: All the options on a conditional form field linked to a Jira Field will not load for customers using the "Report a maintenance issue" form.

Thanks!

[Tomislav Tobijas · Accepted solution]

Hey @Amy Goss ,

Yeah... This is a known limitation and there's an open suggestion related to that: JSDCLOUD-10663: Assets custom field in Form on portal request type should show more than 50 objects 

You might want to leave a vote and comment related to your requirement. Also, you might want to check if there are some 'workarounds' (in the comments) that you may use to bypass this; although I'm not aware there's any at the moment 👀

Cheers,
Tobi

[Amy Goss]

Thank you, @Tomislav Tobijas

At least it's not just me...😀

[Peter Saulesleja]

Hey, this used to work on our Server.  Unacceptable that this is broken in the cloud

We get 15 out of the 50 or so active projects, and can't use the field to search!