Custom field behavior in portal Edited

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?

1 answer

0 vote
Susan Hauth Community Champion Nov 30, 2017

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


Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Bridget Sauer
Published Mar 09, 2018 in Jira Service Desk

E.L. Fridge's take on education, Jira Service Desk, and creative Jira use cases

...word of mouth, so by 2016, we were working with several other entities on campus to implement Jira Service Desk . The Atlassian motto of “for every team” has really come true for us in this case. We...

1,231 views 2 14
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you