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

Is it possible to create a custom select list field based on people assigned to a project role

Ann Rumenapp

My manager is requesting that a card field be added such that the field select list contains only the people on the project that are assigned a specific role. Is this possible? If so, directions would be appreciated.

I've created custom single select list fields, but how do you get the field options to be variable by project role. This would be a unique list for every project. Using a Jira group would not work since on one project I may be an approver, but on another project I would not be an approver.

Accepted answers

Tobias H

Hi @Ann Rumenapp!

I am not sure such a functionality exists out of the box, I think the quickest way to resolve this is to create a group containing the same people and use that instead.

You could then assign them access to the project via the group, if you want to, and you could use the group as the only ones selectable in the User Picker field.

However, depending on how many members they are in the project, and how often the group changes. (And also whether you could automate this through sync groups from IdP etc.) it might be a hassle to maintain.

unknown

Hi @Ann Rumenapp

as @Tobias H suggested a group would do the trick, but maybe even a "Team" could be beneficial.

If you want all ProjectAdmins to be notified, you could put them in a Project-Admin-Team and reference them with the Team custom field.

Sadly I don't think there is a way to use something that would auto-populate.

Kind Regards

All comments

Tobias H

Hi @Ann Rumenapp!

I am not sure such a functionality exists out of the box, I think the quickest way to resolve this is to create a group containing the same people and use that instead.

You could then assign them access to the project via the group, if you want to, and you could use the group as the only ones selectable in the User Picker field.

Ann Rumenapp

Thank you for this option, I haven't used the User Picker type of field before. I will definitely try this option.

unknown

Hi @Ann Rumenapp

as @Tobias H suggested a group would do the trick, but maybe even a "Team" could be beneficial.

If you want all ProjectAdmins to be notified, you could put them in a Project-Admin-Team and reference them with the Team custom field.

Sadly I don't think there is a way to use something that would auto-populate.

Kind Regards

Tobias H

The user picker is certainly the way to go, and I looked at it just now and you can actually set it to Project Role.

So if you are using a company managed project, there's no need to create a group:

Just select Project Role > [Desired Group]

And it will allow you to select from the users who is part of that role, within the project you are using it from.

Screenshot 2024-10-24 191536.png

Tobias H

You are right, we do not use Teams within our workspace, so I hardly ever think of them.

But that would also be a possible way to resolve this and would make maintenance easier compared to a Group, as it does not require admin rights to configure members.

unknown

Perfect @Tobias H , This looks exactly like whats needed.

For your information @Ann Rumenapp This configuration is found after creating the UserPicker Customfield and then adding a Configuration via:

CustomField - Context and default value - Add User filtering. This will allow only the "Developer" Role (or whatever you want) to be used in the field.

If you want to inform all of the people in this role, then you should try the group picker/group reference or team.

Kind regards

Ann Rumenapp

Thank you for sharing more alternatives! Using a Group or Team would also work, however there are 2 cons to this for my use case.

1) It allows an approver to be able to approve on any project. In my organization this could be a security problem since approvers are project specific and someone could approve something on a project where they shouldn't be an approver.

2) A group needs a Jira admin to maintain the approval group members which change often, my business case needs approver to be managed at the project level of control.

Welcome!

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

Quick Links

Unanswered
Groups
Help

Find more posts tagged with

jira

cloud

jira-cloud