Jonathan is right - user deactivation in JIRA is the right way to address the original use case of removing ex-employees showing up in the user group picker.

I believe this issue can be closed; the new user deactivation feature is indeed the right way to handle this, and this feature request does not make sense anymore--limiting the (default) user picker to users with at least one group would be rather confusing given the new option.

Use the free plugin User Group Picker to filter the users to members of a set of groups, project roles or to a value of a group picker.

Related (partial) fix (regarding ex-employees showing up in user picker fields) in JIRA 5.1: user deactivation feature:

While a JIRA user account has been deactivated, that user:

• Will no longer be able to log in to JIRA.
• Cannot be assigned issues or added as a watcher to issues (whenever issues are created or edited). However:
  • A user who was assigned, was watching or had reported any issues in JIRA before their account is deactivated, will still appear as the respective assignee, watcher or reporter of those issues. This situation remains until another user is specified as the assignee or reporter of these issues, or the deactivated user is removed as a watcher from them.
  • A user who voted on any issues in JIRA before their account is deactivated, will continue to appear as a voter on these issues.
• Will continue to appear on the JIRA user interface with '(Inactive)' displayed after their name, where applicable.
• Can still be used to filter issues in a JIRA search query.
• Will not receive any email notifications from JIRA, even if they continue to remain the assignee, reporter, or watchers of issues.
• Will not count towards your JIRA user license limit. Refer to the JIRA Users global permission explanation on Managing Global Permissions for more information.

Any news on that? We definitely need that only "active" JIRA users with at least jira-user group appear in the User Picker field. It's more & more frustrating that ex exployees can be picked!

Hi All,

Minyaa 2.5 is available and provides now a set of 3 customfields in response to JRA-7659 and this one :

• User Picker by Groups
  
• User Picker by Roles
  
• User Picker by Permissions
  

These 3 Customfields come with :

• PopUp Window for user selection
• User Search by Ajax call
• Usable in Transition
• Validation against each of their settings
• Linkifield Display
• Usable for Notification (Not yet for Scheme Permission)

Download now your free Minyaa Suite 1-month trial !
Vincent
Minyaa Suite Plugin

User picker only contains users in specified set of project roles. I'm voting for it because I need it now.

I agree with everyone to day that users in no groups should not show up in the user picker. Is there a timeframe on this?

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 groups as users has rights.

-JPP

What files are associated with the user picker field? I looked at the "WEB-INF/classes/system-customfieldtypes-plugin.xml" and then looked at the API for "com.atlassian.jira.issue.customfields.impl.UserCFType". Has anyone tried modifying the UserCFType.java to allow only users within a groups or role to be selectable?