Issue Pickers turns a custom field into a JQL-filtered list of work items: one or many, unlimited options, with native Jira links created on pick and kept in sync when someone links or unlinks in Jira.
Jira Cloud, Jira Service Management and the JSM portal · Runs on Atlassian · 30-day evaluation
Search, pick, link, unlink. Repeats.
Each one is a setting, not a script. Scroll to watch the same picker do all five.
A JQL filter decides what appears: active contracts, this category, this project. Expired ones never make the list, so nobody picks them by accident.
No cap on how many work items a picker can offer. It loads a first page and fetches more on demand, like Fix versions does; type a word or a key and the list narrows through Jira's own search.
Single-select for a parent, a contract, an owner. Multi-select for dependencies, affected components, related requests.
Choose a link type and every pick becomes a native Jira link, on create, edit and transition screens and in the JSM portal. Reports, boards and automation see it like any other link.
Someone adds or removes the link on the work item instead of in the field? The picker follows: remove on unlink, add on link, each its own switch. Field and links never disagree.
Three minutes in the real app: create a picker, set the JQL and link type, then pick a work item and watch the link appear. No install needed.
.avif)
Large instances, existing links, automation rules and admins who would rather configure than script.
No limit on how many work items sit behind a picker. Search and paging only fetch what is on screen, so the field stays quick however large the instance grows.
Introducing pickers into a live instance? Auto-fill scans up to 3,000 work items, shows you the candidates and fills up to 1,000 per batch, empty fields only.
Give each project and work type its own JQL, or restrict the picker to the current project, so a single field serves every space. The JQL editor validates as you type.
type = Contract AND status = Activetype = Policy AND status = Publishedproject = currentProject()Set picker values from Jira Automation, add to them without overwriting, copy them between fields, and use the picked work item's own fields in your rules.
For people who think in names, not keys, hide the key in the picker, the view, or both, and hide the status too. Search and linking keep working underneath.
The other picker app on the Marketplace, and Jira's own links, side by side with what admins ask us about most.
| VIP.LEAN Issue Pickers | Issue Picker for Jiracodecentric | Native issue links | |
|---|---|---|---|
| Options in one picker | UnlimitedNo cap on options | Up to 2,000Documented limit, for performance | EverythingNo filtering |
| Filter what people can pick | JQL, per contextPlus restriction to the current project | JQL, per contextDynamic placeholders on create and transition screens | No |
| Link created on pick | YesCreate, edit, transition and JSM portal | YesWhen the field is saved | Manual |
| Links changed in Jira, field follows | YesAdd on link and remove on unlink, each its own switch | Not availableField to link only | – |
| Fill fields from existing links | Bulk auto-fill in the appCandidates listed first, 1,000 per batch | CSV export and importBetween instances, by hand | – |
| Jira Automation | Set, extend, copyUse the picked work item's fields in rules | Via smart values | Yes |
| Runs the search as | The app or the current userOne switch per field | The app or the current userAdmin's choice per field | The current user |
| Best when | Large instances, existing links to adopt, field and links that must never drift | Placeholders in JQL matter more than list size or two-way sync | A handful of links, added by hand |
Compiled from the vendors' public documentation as of September 2026. Products change; if we got something wrong about yours, tell us and we'll fix it. Issue Picker for Jira is a product of codecentric AG.
ScriptRunner's Issue Picker field has no counterpart in Jira Cloud, so its values stay behind. The Jira links it created travel with the Cloud Migration Assistant, and that is all Issue Pickers needs.
We map your Data Center pickers with you before the cut-over. Plan the picker migration
Install from the Marketplace, then book a free working session: we'll set up your first picker, the JQL and the link type with you. Solution Partners get stackable discounts of up to 30%.
Questions first? Read the docs or open a support ticket.