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
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'm using custom Cascading field in Jira Service Management request form in the Jira Portal. Is there any way or workaround of using the Cascading field informationto expand alternative fields for the requester to choose?
I know that Cascading fields cannot be added to Forms, which would give more interactive experience for the requester with conditional Sections. Instead, Cascading field can only be added to Request form: Add a conditional field to a service project | Jira Service Management Cloud | Atlassian Support
Why would you not just use the conditional sections in the form?
If I use the conditional sections in the form, I cannot map any form field to Cascading custom field in Jira. I want specifically to map the field and not build the selection list inside the form, since the field value is used in several automation/Slack channel rules.
But I'm trying out now a workaround, with splitting Cascading field values; hierarchy level 1 in one dropdown custom field and level 2 in another dropdown custom field. This way I'd be able to map the form fields and custom fields and use conditional sections.