|
[
Permlink
| « Hide
]
Jeff Turner [Atlassian] added a comment - 11/May/06 04:54 AM
Clarifying the summary.
This would really be helpful when working with a lot of big projects like in our enterprise. These projects are often organized in teams with different responsibilities and changing crews.
Sometimes participants come from a non-technical background and do not know the correct user groups to filter by when working with user picker fields. We have a large amount of user groups and the login names of our users are numeric IDs (for technical reasons). Clearly, this does not improve the situation. So limiting a user picker to a constellation of user groups in the first place would make many processes easier to go through. I have the same problem. I don't want ex-employees showing up in the list, I only want current users of the system.
I also have duplicates due to importing data from other systems. I have deactivated the users by removing them from al the groups but they still show up in the dropdowns and enviably they get selected. Is this issue going to be address any time soon? I have the same problem.
I add a user picker at the workflow process but it's problematic, I must have only specific group of users hi I realy need this option to. I have the same problem.
thank you Efrat We have the same problem. We use the user picker in a custom workflow and it shows ALL GROUPS, including our "inactive users" group (since you can't delete a user if they've created issues, etc). A user shouldn't be able to send an issue to someone who has been "removed" from the system.
The user picker for the watchers screen, also includes ALL groups. So it's possible for one of our users to add an "inactive" user as a watcher to an issue. Solving this issue will solve Daniel's issue as well as other problems.
The user picker I would like to have is customizable project-wide (using contexts) and able to be limited to users with a certain constellation of groups. At this moment we have some 550 users in 20 projects. Currently, choosing a user erroneously who is not in the same project is easy to happen. If that happens during a workflow transition (maybe causing a post function to assign the issue to the chosen person), an administrator has to come and fix it. Apart from this, a dialog showing all users in the system makes it quite unlikely having the user you want to choose right among the first 20 choices. Fact
 :JIRA 3.7 will allow global roles populated with users and groups on a per project level (check  ).
Idea Question Updating summary to mention roles. Limiting to a role's members would allow the list to be different for each project.
To limit User Picker field to Project Roles is an excellent idea.
External customers and internal users are all mixed up into a same user database. so it's really a big security issue for me right now, and for everyone who use Jira for customer suppport I believe. Even I tell our support staff to use the group filter before picking users but Atlassian need to help us to fix this "nightmare". Drop down list would be much better.
Exactly like "Assign to" field. I think the correct behavior for the user picker would be to show only users which have permissions for the current project.
We have multiple unrelated projects with different customers and we would prefer if customer A could not see that we are also working for customer B. It would also get a lot easier to pick someone from the user picker if I only have to choose from the people related to the current project. We altered the User Picker plug-in and made it configurable.
After creating a custom field with this new Multi User Picker type the admin then can configure it with only restricted/desired groups and it will display by default the members of the fisrt group in the list (instead of Any as in the current User Picker plug-in). If not configured it will display normally all groups as currently. This certaintly can not solve all everybody problems but solved mine. Vinh-Thach, is it possible that you share the customizations with us?
Stefan,
I posted it on the forum Please feel free to post any question or suggestion on this forum thread. It's a serious operational limitation for company wide deployment where a large number of projects and users log in to the system. A modified user-picker on a project role basis is needed urgently.
This feature is really important. No serious company may use JIRA if it doesn't allow to protect company privacy, which includes names of all employees working on the project.
My company (700+ developers) will not buy JIRA if this problem is not fixed. Since this problem is 1.5 year old, I think you should handle it with higher priority. Hi,
This usability issue, because we have to disable user picker and security risk, if we not disabling it. User picker should show only those users, which are in same project (and also possibility to limit it to only to same groups) as users has rights. -JPP When I open a new issue in my JIRA and the user (a customer of ours) try to assign to somebody, the listbox shows all my registered users, and not the only ones that work on that specific project. I don't want this, so I guess this improvement might fix this.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Open
Major
Limit user picker to members of certain groups / roles
:
: