In a recent tutorial session, Aaditya Kumar demonstrated how to resolve historical limitations in Jira Cloud automation regarding cascading select fields. For years, users struggled to copy cascading select fields between issues using standard automation, as the child option could not be selected without the parent value.
Understanding the Challenge
Cascading select fields require a two-tiered structure: a parent value (e.g., 'Hardware') and a child value (e.g., 'Laptop'). Older automation rules failed to handle this hierarchy, leading to the assumption that automation for these fields was impossible.
The Solution: Advanced JSON Editing
Modern Jira Cloud automation enables a workaround by bypassing the visual field editor in favor of advanced field editing with JSON. By using custom field IDs rather than display names, administrators can precisely define the data structure.
Implementation Steps
- Locate the Custom Field ID: Navigate to Jira System Settings > Fields to find the unique ID for the cascading field.
- Configure JSON Payload: In the automation rule, use the 'More Options' section to input JSON. Set the 'value' for the parent and a nested 'child' component for the secondary option.
- Utilize Dynamic Smart Values: Replace hardcoded values with smart values like triggerIssue.fields.Category.value and triggerIssue.fields.Category.child.value to ensure the rule remains flexible.
Best Practices
- Use Precise IDs: Always use the unique custom field ID, as using the field name will break the automation.
- Verify with Audit Logs: After turning on the rule, use the audit log to confirm that values are populating correctly.
- Expandable Workflows: This approach is perfect for cloning support requests, synchronizing cross-project issues, and copying metadata.
