nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Scriptrunner Custom Script field Multi-picker

Matt Donagan

Creating a Jira screen for new users requests. I need to create a field that is multi-picker that lists the current Jira projects, so the person requesting the account can pick which projects they need access to, and populate the ticket accordingly.

I am certainly not a programmer and I can't find anything out there like this.

Any help appreciated

Thanks,

Matt

Accepted answers

PD Sheehan

You can create a scriptrunner script field using the "Custom Picker" option.

Using the "Show Snippet", I grabbed the example for Version picker, and converted the suggested configuration code to make it work as a project picker:

import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.project.Project
import com.onresolve.scriptrunner.canned.jira.fields.model.PickerOption
import org.apache.commons.lang3.StringUtils

def projectManager = ComponentAccessor.projectManager

validate = { Project project ->
    !project.archived
}

search = { String inputValue ->
    projectManager.projectObjects.findAll {
        !it.archived && (StringUtils.containsIgnoreCase(it.name, inputValue) | StringUtils.containsIgnoreCase(it.key, inputValue))
}
}

getItemFromId = { String id ->
    projectManager.getProjectObj(id.toLong())
}

toOption = { Project project, Closure highlight ->
new PickerOption(
value: project.id.toString(),
label: "$project.name ($project.key)",
html: "${highlight(project.name, false)} (${project.key}) ${getLozenge(project)}",
    )
}

renderItemViewHtml = { Project project ->
    "$project.name ($project.key) ${getLozenge(project)}"
}

renderItemTextOnlyValue = { Project project ->
    "$project.name ($project.key)"
}

String getLozenge(Project project) {
if (project.isArchived()) {
'<span class="aui-lozenge aui-lozenge-subtle">Archived</span>'
    } else {
'<span class="aui-lozenge aui-lozenge-current aui-lozenge-subtle">Active</span>'
    }
}

You can find more details in the documentation: https://docs.adaptavist.com/sr4js/6.58.1/features/script-fields/built-in-script-fields/custom-picker?utm_source=product-help

All comments

PD Sheehan

You can create a scriptrunner script field using the "Custom Picker" option.

Using the "Show Snippet", I grabbed the example for Version picker, and converted the suggested configuration code to make it work as a project picker:

import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.project.Project
import com.onresolve.scriptrunner.canned.jira.fields.model.PickerOption
import org.apache.commons.lang3.StringUtils

def projectManager = ComponentAccessor.projectManager

validate = { Project project ->
    !project.archived
}

search = { String inputValue ->
    projectManager.projectObjects.findAll {
        !it.archived && (StringUtils.containsIgnoreCase(it.name, inputValue) | StringUtils.containsIgnoreCase(it.key, inputValue))
}
}

getItemFromId = { String id ->
    projectManager.getProjectObj(id.toLong())
}

toOption = { Project project, Closure highlight ->
new PickerOption(
value: project.id.toString(),
label: "$project.name ($project.key)",
html: "${highlight(project.name, false)} (${project.key}) ${getLozenge(project)}",
    )
}

renderItemViewHtml = { Project project ->
    "$project.name ($project.key) ${getLozenge(project)}"
}

renderItemTextOnlyValue = { Project project ->
    "$project.name ($project.key)"
}

String getLozenge(Project project) {
if (project.isArchived()) {
'<span class="aui-lozenge aui-lozenge-subtle">Archived</span>'
    } else {
'<span class="aui-lozenge aui-lozenge-current aui-lozenge-subtle">Active</span>'
    }
}

You can find more details in the documentation: https://docs.adaptavist.com/sr4js/6.58.1/features/script-fields/built-in-script-fields/custom-picker?utm_source=product-help

Matt Donagan

Thank you

Oskar Austegard

Thanks for this, Peter. Do you know of any concise documentation that clearly communicates the functions that are expected to be implemented in a configuration script?

The ? button for the configuration screen shows that the following are accessible, but it is not clear which may be required for an implementation

log

multiValueDelimiter

allowJavaScript

maxRecordsForSearch

highlightMatchesWordPrefixesOnly

disableTextIndexing

getPlaceholderString

renderViewHtml

renderColumnHtml

renderTextOnlyValue

validate

getItemFromId

toOption

renderItemViewHtml

renderItemColumnViewHtml

renderItemTextOnlyValue

Notably absent is `issue` which is available in a simple scripted field.

My use case is to access (a subset of) Components in the current project, which would be doable if I could find a way to refer to the current issue/project/component list

I find the Adaptivist documentation to be frantically dispersed...

PD Sheehan

I'm not aware of any documentation other than the page I shared above.

But based on that, the "issue" variable is only defined in the context of the search method you see in the '?' popup.

So if you want to get a filtered subset of components, you can set the configuration script to:

search = {String inputValue, Issue issue->
   def projectComponents = ComponentAccessor.projectComponentManager.findAllForProject(issue.project.id)
   return projectComponents.findAll{ <filter criteria for your subset>}
}

OpsTech Support

Hi there,

I saw this request for a multi-project picker custom field, it's a very common need since Jira only offers a single Project Picker out of the box.

We have an app on the Atlassian Marketplace called Multi Project Picker Fields that solves this exactly:

- Select multiple projects in one custom field
- Fully Forge-based → more secure and native feel
- Works in issue view, create, edit, transitions, and bulk edit
- Field context configuration (filter by category/type or specific projects)
- Native JQL support + clickable projects in read-only view
- Shows “Archived” or “Not found” labels when needed

It’s a clean, modern solution for use cases like cross-project dependencies, affected projects, or portfolio tracking.

You can try it here:
https://marketplace.atlassian.com/apps/1488462522/multi-project-picker-fields

Full documentation and setup guide:
https://opstech-apps.atlassian.net/wiki/spaces/MPF/overview

Happy to answer any questions if you give it a spin!

Cheers,
OpsTech Apps Support

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

scriptrunner

jira

jira-server