How to Limit Dropdown Options in Jira (Priority, Resolution, Components)
Your Jira Priority dropdown shows five options for every issue type. Users pick "Medium" when they mean "Critical" because the list is too long to think about. Your Resolution field offers options that do not apply to the current issue type. The data looks complete, but the values are wrong. The fix is dropdown filtering — showing only relevant field options based on issue type, workflow status, or user role.
This guide shows how to limit dropdown options in Jira — by issue type, by workflow transition, and by user permission — so users only see choices that make sense in their current context.
What You Will Implement
Three option-filtering rules: limit Priority by issue type, limit Resolution by workflow transition, and restrict Critical priority to managers only. Each rule reduces noise and prevents invalid selections.
Why long dropdowns hurt data quality
Every option in a dropdown is a decision point. The more options, the higher the chance of a wrong pick — especially under time pressure.
Wrong selections
Users scan a long list, pick the first option that seems close enough, and move on. "Medium" instead of "High" does not look like an error until triage.
Irrelevant options
Bug resolutions like "Cannot Reproduce" appear on Story closures. Users pick anything to close the issue, polluting resolution reports.
Priority inflation
Everyone sets Critical because it is the first option in the list. Without guardrails, priority loses meaning within weeks.
The fix is not training or documentation. The fix is limiting dropdown options — removing choices that should not be there in the first place.
What can be filtered
System fields
Priority, Resolution, Fix Versions, Affects Versions, Issue Type, and Parent. These are the most common targets for option filtering.
Custom fields
Single Select, Multi-Select, Radio Buttons, and Checkboxes. Any custom field with a predefined option list can be filtered.
Scenario 1: limit Priority by issue type
Bugs should only use Critical and High. Tasks and Stories get the full range. This prevents documentation bugs from being marked Critical and blocking the sprint.
Test cases
Combine with Set Value for a smart default
Pair this rule with a Set Value action: pre-fill Priority = High when Issue Type = Bug. Users still see Critical and High in the dropdown, but the default is already set — reducing one decision to zero.
Scenario 2: limit Resolution by issue type on transition
When closing a Bug, show technical resolutions. When closing a Story, show completion resolutions. Users never see options that do not apply.
Test cases
Test cases
Clean resolution reports
Every Bug has a technical resolution. Every Story has a completion status. Reports reflect real outcomes, not random picks.
Faster closure
Two options instead of eight. Users select the right resolution in one click instead of scanning a list they do not understand.
Scenario 3: restrict Critical priority to managers
Only users in the Managers group can set Critical priority. Everyone else sees High, Medium, and Low. This prevents priority inflation without adding approval workflows.
Test cases
This is the only scenario in this guide that uses a user-based condition instead of issue type or status. It demonstrates that option filtering works on any condition type — including who is filling the form.
Watch out: existing values outside allowed options
If an issue already has Priority = Critical and a non-manager edits it, the current value is preserved. The rule only limits what can be selected — it does not remove values already saved on the issue. This prevents accidental downgrades when non-managers edit existing Critical issues.
Limiting options vs other actions
Limit Options
Field is visible, but only allowed values appear in the dropdown. User can still interact with the field — just with fewer choices.
Hide Field
Field disappears entirely. Use this when the field is irrelevant, not when you just want fewer options in the dropdown.
Use Limit Options when users need to pick a value but should not see every possibility — Priority filtering, Resolution filtering, version restrictions.
Use Hide Field when the entire field is irrelevant for the current context — like hiding Story Points on Bug issues. See the defining actions guide for all available action types and when to use each.
What to monitor after rollout
Check for blocked selections
In the first week, monitor if users report that they cannot find an option they need. This usually means the rule is too restrictive or a new option was added to Jira but not to the rule.
Measure data quality improvement
Compare Priority and Resolution distributions before and after. Look for fewer "wrong" selections: fewer Mediums on critical bugs, fewer "Won't Fix" on Stories.
Expand to more fields
Start with Priority and Resolution. Once the team adapts, apply the same pattern to Fix Versions, Components, or custom select fields.
Common questions
Can I limit options on custom select fields, not just Priority and Resolution?
Yes. Dynamic Screen Rules supports limiting options on any single-select or multi-select custom field, including radio buttons and checkboxes. The configuration is the same: define the condition, choose the Limit Options action, and specify which options should remain visible.
What happens if an issue already has a value that is now outside the allowed options?
The current value is preserved and stays visible in the field. The rule only limits what can be newly selected — it does not remove values already saved on the issue. This prevents accidental data loss when editing existing issues.
Can I limit dropdown options based on another field's value?
Yes. Use a field-based condition to trigger option filtering. For example, limit Priority options when Customer Impact = Yes, or filter Resolution options based on the value of a custom Severity field.
Does this work on Jira Service Management request forms?
Yes. Option filtering works on JSM request forms in the same way as standard Jira create and edit screens. You can limit dropdown options based on request type, priority, customer organization, or any other supported condition.
Shorter dropdowns, better data
Set up your first option filter in under 10 minutes — no scripts, no field configuration hacks.
Start trial on Marketplace