Better JIRA interface for User Access Management

Question

We need the ability to manage our JIRA users more effectively. Our current version (v6.1.6#6162) interface does not allow me to filter out inactive users, so I'm able to focus just on active users to inactivate efficiently. This is affecting our ability to meet internal audit requirements. Ideally a plugin or new interface that allows us to:

* Automatically inactivate users after a set period of inactivity
* Filter the user list by active / inactive users
* Filter the user list by all other attributes on the page
* Sort user list by last login date (Login Details)
* De-activate users without having to go into the edit function/operation

I'm unable to find anything in the Atlassian Marketplace for this.

Joanne · Answer

I came across these recommendations which may be of use when looking for some of these myself - JIRA REST API (https://docs.atlassian.com/jira/REST/latest/) and create an export of specific data or exporting from database https://confluence.atlassian.com/display/JIRAKB/How+to+export+users+to+CSV+from+a+JIRA+application

Michael Kornatzki · Answer

in my opinion it looks realy ugly if one open an issue and the creator named something like 'zzzz...' and that for all deactivated users :(
I have a lot of deactivated users and i want to see the "normal" names if i look at an issue they created or edited before they get deactivated.

Jonas Andersson · Answer

No mention of what authentication method you are using, nor if the users are disabled for all future (user leaving the organisation), so i assume JIRA running against a Microsoft AD.

If removed permanently, just remove something in AD that JIRA would filter on. Our current LDAP filter makes sure that description contains for example "permanent", that a user has a internal phonenumber. If not, the user is filtered out on the next LDAP sync, and user is no longer visable. More about that here:

https://confluence.atlassian.com/jira/reduce-the-number-of-users-synchronised-from-ldap-to-jira-587957108.html

If you are only using an internal database you can always rename the user to: ZZZ-username, to make sure they are grouped at the end of the directory, rather than mixed will all current employees.

This does not meet all your requested features, but should bring you a part of the way there.