Discussions
-
Building Multi-Level Cascading Fields in Jira Cloud: A No-Code Approach
Jira's native Cascading Select field gives you one parent and one child within a single field. The moment you need a third level, or you want one selection to show or hide entirely different fields, you're out of options natively. This article walks through how to solve that — with a concrete example you can follow action…
-
Right by Design: Automating, Building and Guiding Business Processes in Jira
Jira already provides a strong foundation for workflows, permissions, approvals, automation and traceability. With the right extensions around those capabilities, it can also support richer, connected business processes that feel natural to the people using them. To illustrate what is possible, let’s take a very simple…
-
Reducing Custom Field Sprawl with Context-Based Field Labels
If you've managed a Jira instance for more than a year, you know how it starts. A team needs to track something specific, a field gets created. Then another. Then ten more. Before long, you're staring at 300+ custom fields, half of which no one remembers creating. At one of our enterprise clients, the field list had grown…
-
Adapt Options for a Select Field by Work Type in Same Space- No Code Behaviours Builder Show Case
Jira Cloud's field contexts are flexible, but they hit a wall in one specific case: varying the options of a single-select field by work type within the same space. Here's what's missing — and how to work around it without duplicating fields. The use case In the Templates space, we use a custom field Impact with two work…
