Limit "User Picker" field?

[Jositz, Michael (Allianz SE)]

Is there a possibility to limit the JIRA "User Picker" field to active JIRA users? As JIRA does not support deactivationg users and also is not able to rename / merge users we had to create new accounts if User ID chnaged.

But now we run into trouble that the "User Picker" also lists users even if they do not have any permission like jira-user permission. That creates many wrong adressed users at the moment. Any idea?

Thanks Michi

[Simon Kegel //SEIBERT/MEDIA]

Hey there,

you could restrict you permission scheme and not allow deactivated users there - so they won't come in the user picker. 
 
New Group / Role f.e. "Active Users" and set all of theme in this - and this could be a requirement for being assigned in internal projects?

Hope this could help.

Greets
Simon 

[Jositz, Michael (Allianz SE)]

LDAP, stored in our AD (JIRA Delegated Authentication Directory). We also have some "JIRA Internal Directory" users, but 98% are LDAP accounts.

[Jositz, Michael (Allianz SE)]

Thanks Matthew, it's the 3rd option we use with existing custom field. We do not use Crowd.

<address>Change the jira configuration so that only active users show.</address><address> </address>

How can I do that?

[MatthewC]

What version of Jira? Where are the users stored? Internally? LDAP?

[MatthewC]

If it's a custom field you could use the User picker from Customware & restrict it to Jira users.

https://plugins.atlassian.com/plugin/details/15453

[Jositz, Michael (Allianz SE)]

We used the JIRA internal "User Picker". i checked the plugin, but therefore it is neccessary to create a new custom field. Problem: We already heavily used the default JIRA "User Picker" and can't change that to another field...

[MatthewC]

In that case, the answer is "it depends".... if it's the assignee field then you can restrict who appears in there by using the permission scheme to restict the list of "assignable users".

If it's the reporter then there isn't much else you can do with that.

If it's an existing custom field of user picker type then you only have two choices.

1. Create a new user picker field that restricts to a group & update all your filters, dashboards, screens & workflows to use the new field.
2. Change the jira configuration so that only active users show. If you have Crowd you can disable users

How are you connecting to your authentication source?

[MatthewC]

Ok, since you're using LDAP and you want to restrict the account names which are visible in Jira you're going to have to use LDAP filters to cut down the number of accounts Jira can see in your LDAP. Even if you're not using Crowd it's worth looking at this:

http://confluence.atlassian.com/display/CROWD/Restricting+LDAP+Scope+for+User+and+Group+Search

It may also be worth reading this: http://confluence.atlassian.com/display/JIRA/User+Management+Limitations+and+Recommendations

Without knowing all the details of the setup & how your LDAP is structured then it's difficult to help more.

If there is nothing in your LDAP profiles you can use in a search, one other solution is to setup your own LDAP server (OpenLDAP) and put it between Jira & the main LDAP server. You can then replicate the data across into your own server, modify the schema to include an attribute which you can use in an LDAP search to cut down the number of users.

[Jositz, Michael (Allianz SE)]

I think it's not possible here because we only use "JIRA Delegated Authentication Directory" which means that we create the user in JIRA with username as LDAP name. So we use LDAP only for authentication, but users are still maintained in JIRA. We can't use full AD user management because if we did users would disappear in JIRA if they are deleted in AD. This would solve the problem I raised here, but e.g. in JIRA the users would no more be available for history. What we also miss in JIRA which is I think related to that issue: https://jira.atlassian.com/browse/JRA-2220 (Deactivate user).