Custom field behavior in portal

[Tim Saunders]

I have a custom field that only appears on the screen when another field value is selected. This works fine in the create and edit screens within Jira but fails miserably in the portal; the optional field appears all the time (and ignores the "mandatory" setting as well). It appears that Service Desk is ignoring the javascript in the description of the custom field. I've read that this may be a problem, Is this true and is there a workaround?

[Susan Hauth _Jira Queen_]

Hi Tim,

Yes Service desk does not pay attention to rules, conditions, scripts that work on the Jira side.   We use plugin Extension for Jira Service Desk.  Works beautifully, but is only on Server and is not free.

Hope that helps

Susan