Cascading fields (one field based on value of other field) within Jira workflow screen

[Simon Sahli]

Hi Atlassian community,

I have had several time the requirement that for a Jira workflow there are two fields to be added to the SAME transition, but the second field shall only be shown depending on the value of first field (cascading fields).

Example:
There is a new YES or NO type of field (single choice) that shall be added to NEW to WORK IN PROGRESS transition screen.
Only if the users chooses YES as a response for this field then another field shall appear in the workflow screen where the users explain WHY they have chosen YES for this field. If they have chosen NO for the previous field then the why field does not need to appear.

I don´t think that Jira workflow screens are flexible when it comes to displaying fields, right?
If that assumption is right, then what is the best practice to deal with this kind of requirement?

I am so far just showing both fields in the workflow screen and I mention in the field description that the second field only has to be filled in if the first one = YES.
However this is not so ideal, since first, I cannot make the second field mandatory and it also adds more fields that are often not relevant.

Please let me know if you have any proven best practice approaches for this kind of described situation. 
Thanks in advance!

Best regards,
Simon

[Adolfo Casari · Accepted solution]

@Simon Sahli- this is an addon that can help you here:

https://docs.adaptavist.com/sr4jc/latest/features/behaviours/example-behaviour

[Simon Sahli]

Hi @Adolfo Casari
thanks for your response!

We are actually using Scriptrunner, but I haven´t looked into the behaviour part and I needed to install the app first.

I looked through the documentation and their videos and yes they have the functionality I am looking for (5. Behaviours demo: Conditionally show/hide custom field with ScriptRunner for Jira Cloud (youtube.com)), however this only seems to be doable for the Create and Issue view screen, not for workflow screens. 
Would you agree with this statement or is it still somehow possible to use the behaviour app functionality from Scriptrunner also for workflow screens?

Also there seem to be some current technical restrictions when it comes to behaviours for JSM (unlike Jira Software), which could be a problem, since I am mainly interested in using this for JSM.

Cheers,
Simon

[Adolfo Casari]

@Simon SahliI guess that is right, that is not available for transition screens yet. I suggest you to contact adaptavist support to confirm that.

[Simon Sahli]

Just to conclude this request, it is currently not possible to use the ScriptRunner Behaviours app for workflow screens nor for Jira Service management.
There are however pending request that will hopefully soon implement both features, see:
Support Behaviours in Jira Service Management · ScriptRunner for Jira Cloud Feedback (nolt.io)

Support Behaviours on transition screens · ScriptRunner for Jira Cloud Feedback (nolt.io)