Jira Environment Details:
Jira Datacenter 8.20.14
Hello everyone,
I have been requested to create a custom field so that a user can be selected from a group automatically.
To add context and a use case: I have been requested to create a Issue Type called "Resource Request".
This Issue type is to be used to allow certain members of our management team to create a ticket to request resources for future projects so they can be planned as a ticket.
One of the requests is to select a user from a specific group. For example; the team that approves this request has 4 users. So a request is created the users only have the option of selecting one from the specific management group.
I could just use a Drop down list for this. But from a maintenance and administrative point of view, manual lists are poorly managed generally.
I hope there is a solution to this via either groovy script or Jira automation (We do have a license to the application "Automation for Jira"). I would prefer automation for this as it would be easier to debug and ensure reliability.
Thanks for your time (and hopefully your help).
A user picker field can be limited to a group (or set of groups)
Go to Admin -> custom fields and find your user picker field, and go into the "context" you have set for it. At the bottom of there, there is a link to "edit user filtering" which allows you to set one or many groups to limit the user-picker to.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @NSEU DevOps
If your requirement is to allow only X number of people to create an issue, then why you don't place a validator on that specific request type, that only "members of a selected group" are allowed to create this issue?
And if you have solved already the above and you want a user field that will allow only users from a certain group to be selected, then why you don't user group filtering on that user field?
Is there something else that I'm missing on your requirement?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Alex Koxaras -Relational- with regards to:
then why you don't place a validator on that specific request type, that only "members of a selected group" are allowed to create this issue?
Its not for the creation. It's for the approval. Each project has a specific member from that group (for example; any project under the customer "Ferrari" would have one responsible project manager "Member A", "Porsche" will also have its own project manager etc etc.
I have considered adding a transition to a workflow but the aim is for the management team to select the correct responsible person.
With regards to:
And if you have solved already the above and you want a user field that will allow only users from a certain group to be selected, then why you don't user group filtering on that user field?
I've resolved this in an incredibly clunky way. Which unfortunately I don't actually like. I want to automate it in a way that a "user picker" limits who can be added as per the group.
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.