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; } } }

Limit Multi User Picker field

unknown

Hi all!

I've been struggling with this question, what do you do to limit a multi user picker field to a certain group or project role? As many of you know, you can limit single user pickers out of the box, but that's not possible with multi user pickers

I thought that Behaviour could achieve it, but I realiased that the line code I use for this works for Select list and Cascade fields, so I guess that I can't use this

Right now I'm using validators, but this is not optimal. What are your thoughts about this?

Accepted answers

Joshua Yamdogo @ Adaptavist

Hi Cristian,

This is not currently possible at the moment in ScriptRunner using behaviours - please see SRJIRA-2986 for information. Note that although that ticket is closed as Won't Fix, the development team will be working on a new system of custom picker fields that will provide equivalent functionality of limiting users/groups for multi-picker fields.

Regards,

Josh

All comments

Joshua Yamdogo @ Adaptavist

Hi Cristian,

Regards,

Josh

unknown

Thank you!

Steven F Behnke

.setFormValue() works just fine for multi-user pickers. What's wrong with that approach? It works well from my point of view.

unknown

.setFormValue is not what I'm asking about, I'm asking about limit the options which appear in the field and, as Joshua said, this is not currently possible with Behaviour.

I'm curious about what other jira administrators do to resolve this.

Welcome!

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

Quick Links

Find more posts tagged with

server

atlassian-marketplace

jira

jira-service-desk

adaptavist

jira-server

jira-service-desk-server