Behaviour‐script filtering cascading select field working in Create screen but not in Customer Porta

[Musthafha Sayyad]

Hello Atlassian Community,

We are using Script Runner for Jira (Data Center v10.3.3) with a behaviour on the “Request” field (customfield_15701) to dynamically filter the parent values of a category (cascading se field) (customfield_10409) based on the request value.

Here’s the key behaviour:

• If Request = “Test”, the parent options list filters correctly and are selectable on the request form.

• If Request = “Packaging”, the parent options list shows but is not selectable on the customer portal (JSM) even after screen refresh.

The same script works fine on the Agent Create screen for both request values but fails only in the portal for “Packaging”.

Script (relevant part):

def RequestField = getFieldById("customfield_15701") def cascadingField = getFieldById("customfield_10409") def RequestValue = RequestField.getValue() as String if (!RequestValue) return def allOptions = ComponentAccessor.optionsManager.getOptions( ComponentAccessor.customFieldManager .getCustomFieldObject(cascadingField.fieldId) .getRelevantConfig(getIssueContext()) ) def parentOptionsToShow = [] if (RequestValue == "Packaging") { parentOptionsToShow = ["Assembly and Finish", "Bumping", "Die Prep", "General", "Intel Foundry Portal", "Packaging Design", "Test"] } else if (RequestValue == "Test") { parentOptionsToShow = ["Die Sort/Wafer Sort", "BackEnd/Final Test (Burn-In, Class, SLT/PPV)", "FIFA", "PHI", "Miscellaneous", "Tester HW/SW, Module"] } def allowedParentOptions = allOptions.findAll { it.value in parentOptionsToShow } cascadingField.setFieldOptions(allowedParentOptions)

Issue Details:

• On agent screen: Both "Test" and "Packaging" filter & allow selection of parent options – works as expected.

• On customer portal:

  • When Request = “Test”: category options are filtered and selectable.

  • When Request = “Packaging”:  category options are filtered and visible, but cannot be selected (dropdown appears, but user cannot choose an option).

• Field context is identical for both request values as far as I’ve verified.

• The behaviour is mapped for both the issue types and the portal request type (as per our mapping).

• I suspect this is a UI or context limitation in the portal or with cascading select + behaviours.

Questions:

1. Is this a known limitation of behaviours for cascading select fields in the portal context?

2. Are there any settings/configuration differences for cascading select fields on portal request types that would explain why the options become non-selectable for one request value but not the other?

3. Are there recommended workarounds (e.g., alternative scripts or using single-select fields instead) specifically for portal use in Data Center v10.3.3?
   
   

   Additional configuration info:

   • On the portal screen, the “Test” value is set as a default value in the Request field for that request type.

   • We also have a behaviour in place to hide the “None” option in the Request field when applicable.

   • We’re using a Dynamic Form for the Category → Sub-Category cascading field (customfield_10409), meaning that based on the chosen category/sub-category, another field will appear and become required. This additional logic is working independently and is not related to the current issue (it’s just given for context).

   
   
   Best,
   Musthafha

[Marc - Devoteam]

Hi @Musthafha Sayyad 

Welcome to the community.

Behaviours can't be used on a JSM portal, this is only for agent side.

You could use the app Proforma forms to create forms for portal requests and make use of conditions in a form based on choose options

Also context options are based on the issue type, not on request type, as a request type uses an issue type.

BTW, you asked the same question on FRiday, https://community.atlassian.com/forums/Jira-Service-Management/Portal-behaviour-issue-with-Request-Category-Subcategory/qaq-p/3134773 

[Radek Dostál]

No, behaviours have JSM mapping which works more or less the same way as they do on JSW.

(If cascading is special as per the referenced answer then so be it, but never had problem setting up jsm behaviours.)

[Marc - Devoteam]

Hi @Radek Dostál 

In a sese correct, but Behaviours won't work from a customer portal side.

If you are on the portal an creating a request a behaviour won't work. Behaviours work from the agent side in the project, as that is creating a work item in the regular way.