-
Suggestion
-
Resolution: Unresolved
-
334
-
179
-
Update 17 October 2023:
The watchers of this ticket may be interested in this post: Improvements to Browser User permissions (User Searchability by Project). Please add any questions or comments there.
This is an improvement request related to JRA-7659: "Limit user picker to members of certain groups / roles". The current implementation of limited user picker does not work on system fields of Reporter and Assignee, and does not limit the users displayed in the @ mention dialog.
The Jira Service Management equivalent of this ticket may be found here: JSDCLOUD-10055 – Don't show users (or Portal Only Customer) who doesn't have Jira application access to appear on reporters and project roles list
- incorporates
-
JRACLOUD-81318 Hide or filter out portal only users (JSM Customers) who don't have Jira application access to appear on assignee, reporters, project lead and project roles list
- Gathering Interest
- is duplicated by
-
JRACLOUD-7776 When adding watchers, the user-picker dialog should only show users who have access to the project.
- Closed
-
JRACLOUD-40963 Allow user filtering for User Picker (multiple users) custom field type
- Closed
-
JRACLOUD-42446 Restrict Reporter Field to only users with Create Issues Permission
- Closed
-
JRACLOUD-44316 As a user I would like to have the same UI for "limited user picker" custom field as System Assignee field.
- Closed
-
JRACLOUD-60427 Remove ability to add portal user as reporter
- Closed
-
JRACLOUD-63213 User can add any user from JIRA as reporter
- Closed
-
JRACLOUD-69568 Hide specific users or group from a user picker field
- Closed
-
JRACLOUD-76780 Customers shouldn't be suggested on User Picker custom fields on non-Jira Service Management projects
- Closed
-
JRACLOUD-77995 Allow user to browse users and groups for user picker fields based on project permissions
- Closed
-
JSDCLOUD-12642 Limit Reporter field to customers added to the project
- Closed
-
ID-8127 Show only users with project access rights in Find Issues-User Browser
- Gathering Interest
- is related to
-
JRACLOUD-80908 Users who does not have access to the product is available under user picker fields like reporter, watcher
-
- Closed
-
-
JSDCLOUD-8649 Customer without permission to project can be added as a reporter of a request
-
- Closed
-
-
JRACLOUD-7659 Limit user picker to members of certain groups / roles
- Closed
-
ID-8130 Prevent System Users to Show on User Picker fields
- Gathering Interest
-
JRASERVER-36896 Limit User Picker to members of certain groups/roles in System Fields
- Gathering Interest
-
ACE-4000 Loading...
- relates to
-
JRACLOUD-81820 User filtering (single user picker) does not work in the new issue view
-
- Closed
-
-
JRACLOUD-40963 Allow user filtering for User Picker (multiple users) custom field type
- Closed
-
JRACLOUD-76780 Customers shouldn't be suggested on User Picker custom fields on non-Jira Service Management projects
- Closed
-
JRACLOUD-78904 Limit User Picker based on value of other fields
- Closed
-
ID-8129 Ability to restrict what Projects, users or groups appear in @-mention results
- Gathering Interest
-
JRACLOUD-81318 Hide or filter out portal only users (JSM Customers) who don't have Jira application access to appear on assignee, reporters, project lead and project roles list
- Gathering Interest
- blocks
-
ACE-3992 Loading...
- is addressed by
-
ENT-1690 Loading...
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
[ID-8128] Limit User Picker to members of certain groups/roles in System Fields in Jira Software, Jira Work Management, JIRA Service Management and Atlas
Support reference count | Original: 178 | New: 179 |
Support reference count | Original: 177 | New: 178 |
Support reference count | Original: 176 | New: 177 |
Support reference count | Original: 175 | New: 176 |
Support reference count | Original: 174 | New: 175 |
Support reference count | Original: 173 | New: 174 |
Support reference count | Original: 172 | New: 173 |
Support reference count | Original: 171 | New: 172 |
For some of our Jira projects, we would like to be able to limit Assignee selection to members of the selected Team (as in the Atlassian team associated to the issue). For instance:
"Team A" has three members - Sam, Jan, and Ivan. Once the value of "Team A" is selected, the user would then only be able to select Sam, Jan, or Ivan in the assignee list. Ideally, we'd be able to determine per-project whether the Team field would filter the Assignee field.