A cascading select for Jira Cloud that shows on the portal, imports your existing values, and searches by level.

An N-level cascading field built on Forge — region → country → office, product → component → version, as deep as you need. Visible on the Jira Service Management request form. CSV import with no size ceiling. JQL on any level, not just the whole path.

In development. Not on the Marketplace yet. We are building it against the three things Jira admins tell us break in the cascading-select apps they use today: fields that don't appear on the customer portal, imports that fail on real-world option trees, and values you can't search by level. If that is your situation, tell us about it below.

No spam, no sharing. We'll write when there is something to try, and we may ask you a few questions first.

What it will do

  • Any depth. Three, four, five levels — one field, one option tree, edited by an admin without a redeploy.
  • On the portal. Renders on the Jira Service Management request form, so customers pick the right path at intake.
  • Import that works. Bring your existing tree in from CSV, whatever its size. Export it back out, re-importable.
  • Search by level. Field.level2 = "Berlin" in JQL, not only a text match on the whole path.

Built on Atlassian Forge, so it runs on Atlassian's infrastructure and stores only your option tree and selected values — no personal data, no external servers.

Who is building this

An independent developer, not a company, and not affiliated with Atlassian. This page exists to find out whether enough teams need this before it is built — which is why the form asks about your site. If you would rather talk than fill in a form, say so in the form and leave your email — we reply to every one.