You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I have come across this JSON but don't know how to hide or unhide a custom field. Field name is "Impacted Service:" and I want to hide it based on user selecting "Other:" in another field.
{
"update": {
"Impacted Service:": [
{
<<<<<<How to hide the field>>>>>>>>
}
]
}
}
The only supported action here seem to be "set" which is not what I need.
That's what my automation flow look like:
I'm a relative newbie to Jira Administration, but there is a custom field type called "Select List (Cascading)". Might that solve your problem?
This feature of cascading select list is helpful if you have a field (say city selection) dependent on the parent field (say country selection). It cannot be used as a hiding/unhiding requirement. Anyhow, I have got what I needed by using custom Forms which is an in-built feature in Jira Service Management Cloud.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Unfortunately, the Automation for Jira functionality doesn't support field hiding/unhiding based on other custom field's value. Therefore, automation rule will not work for you.
Currently, the only thing I know that it may work in the Cloud env is ScriptRunner for Jira add-on Behavior component. However, the vendor is still working with Atlassian to develop the full capability to provide the functionality just like what they have for the DataCenter (on-prems) env.
I would recommend you to search Atlassian Marketplace for other third party add-ons that may provide the functionality -
Example
Lastly, out of the box in JSM, it is not possible.
Hope this helps.
Best, Joseph Chung Yin
Jira/JSM Functional Lead, Global Technology Applications Team
Viasat Inc.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Joseph Chung Yin , I have got the ScriptRunner and the bahavior add-ons added. My script is shown above. What else is missing ? Its not accepting SetVisible() methods saying "Property 'setVisible' does not exist on type 'Field'. Did you mean 'isVisible'?(2551)"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It is "setHidden" is the method and not "setVisible".
Hope this helps.
Best, Joseph
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Joseph Chung Yin, I just changed the affected field to be "Other impacted service" and the code errors seems to have been gone. Even setVisible() is looking acceptable.
It doesn't seem to work regardless. Just to share more information, I have this kind of Incident raising form (refer below)
and I want the "Other Impacted Field" to appear (become visible) whenever the user selects "Other" in "Affected Service" field.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please note that Behavior component for Cloud is still under enhancement between the vendor and Atlassian. So please refer to the following vendor documentation for is supported at this time (especially dealing with custom fields) - https://docs.adaptavist.com/sr4jc/latest/features/behaviours?_ga=2.183995044.340474686.1675660571-414402845.1665030927#id-.BehavioursvCurrent-BehavioursSupportedFunctionsBehavioursSupportedFunctions
Best, Joseph
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.