Our new app, License Optimizer, can manipulate the application access in real-time granting access only to the users who are active. That means you don't have to monitor and manage the inactive users for yourself, the app will do it for you:
https://marketplace.atlassian.com/apps/1224199/license-optimizer-for-jira

Currently, it is available only for Jira Server, but we are working on the Data Center version.

Here is a Jira cloud addon developed by my company that allows you to search, filter and bulk delete users:
https://marketplace.atlassian.com/apps/1221764/user-management-by-toros

In addition, it allows you to search for inactive users (users who haven't login in a while) and perform some bulk operation.

How difficult is it to add a checkbox to filter out who is active vs. inactive? This is another brain-dead move by Atlassian. Yes, it would require some development and testing, but this seems like the kind of administrative value-add that could likely be accomplished in a day. Just add a checkbox for "only include active users." I've seen comments elsewhere about how improving the administrative experience in Jira is a high priority for Atlassian. This is a very simple addition that would really help.

kbaratakke can you please have your customer contact me at boris@atlasauthority.com and I can take a look at what is going on? I have tested the add-on with 20k users and had no performance issues (beyond JIRA's underlying ones).

This need arose for me again and I found myself at this ticket once more.  I was about to rant but I see that I've already done that in the past, so let me just say that the decision to close this ticket without any consideration to a REAL FUNCTIONAL FIX WITHIN THE UI instead of having to go f**k around in the db like a gorilla performing brain surgery with a spoon is absolutely unacceptable.

@Boris Berenberg, I have replied

Thank you feedback1534286591!

nmareedu1585045417, I just sent you an email

@Boris
I have installed this plugin on a test server (Jira 6.4.13) and it is showing all are Active and it is not true in reality.

@Boris: I like the change – thank you!

We just released a new version. You can see it at https://marketplace.atlassian.com/plugins/cr.tin.ActiveUserFilter.active-user-filter/server/overview It improved the phrasing per vic.tsushima's suggestion and adds the ability to export the results to CSV. You can see it at https://marketplace.atlassian.com/plugins/cr.tin.ActiveUserFilter.active-user-filter/server/overview

We have built an add-on which will allow you to perform this filtering: https://marketplace.atlassian.com/plugins/cr.tin.ActiveUserFilter.active-user-filter/server/overview
Please let me know if you have any feedback via feedback@tin.cr

Would be nice to have this.

You can use my JQL custom function:
https://jirasupport.wordpress.com/2015/12/18/custom-jql-function-hasinactivereporter-and-hasinactiveassignee-compatible-with-jira-7/

Hello,

Just following up on my earlier comment - we have not seen sufficient interest in a paid add-on to solve this need. As such we will not proceed with development.

Regards,
Nicholas Muldoon
Arijea

This is not something that should be solved with an add-on. This is some integral part of user management that should be resolved by Atlassian.

Hi watchers,

We're an Atlassian Marketplace vendor that is investigating whether it makes sense to provide a paid add-on to address this feature request for JIRA Server.

If you would be willing to pay for this feature fill out this form before January 20th. We will update this issue again by the 22nd January to let you know if/when we will release a paid add-on.

Thanks,
Nicholas Muldoon, Arijea

I am absolutely with the other people. For administrating people it is a really important feature! Furthermore I do not think that it costs Atlassian more than 2 days to implement that filter option.
Disappointing!

+1
Disappointing, frustrating but not entirely surprised.

@Olivier Croquette: very interesting and unfortunately sad. We are also in the situation where we spend a lot of money for Atlassian on-premises licenses but we miss basic functionality like this for administration, and we are left in the dark.

Oh wow, that's kind of crazy, and sad :/ Thanks for the information, it's really interesting to see...

@Chris Myers: I don't think it has anything to do with the legal status of Atlassian. There are actually many tickets like this one, e.g. many years old, with many votes, but with zero progress. I got so frustrated that I did a small analysis to find out if it was me overreacting, or a real issue at Atlassian. I am know convinced it's the latter, check out the diagrams here

Definitely not trying to jump to conclusions, and really really hoping that my secret worries are unfounded. I've just seen too many things like this happen with other vendors lately that I'm being slightly pessimistic.

Well here's my conclusion: For me, many of the most desirable Marketplace add-ons apply only to the Server edition. This flies in the face of Atlassian not wanting to support the Server edition. I find this "pulling the rug out" from Atlassian's good, long time customers to be disheartening, not to mention how Jira add-on developers must feel.

Atlassian, please make up your mind whether you're going to (really) support Cloud or Server.

Well, lets not jump to conclusions. This is ONE fix that Jira Cloud folks have that Server folks don't. Granted its completely absurd and insulting that this hasn't been made available for Server folks, but maybe there's a good reason for this that isn't being shared for reasons.

+1 at cmyers1

Disappointed to see that support for Jira Server is diminishing. It is not an option for our organization to switch to cloud either due to security restrictions. I hope Atlassian reconsiders.

I've always been an evangelist for Atlassian products (both to users on-campus and other institutions.) And have done so excitedly because they've been a great company to work with, with innovative products, great support, and a good customer focus.

I'm hoping that that's not changing now that they're a publicly traded company. Holding my proverbial breath to see how things move forward, but arriving to work this morning with a number of "won't fix" emails isn't making me feel very optimistic right now :/

Same issue here.
My company won't upgrade to Cloud in the near future (or ever) as I see it. This is just not so professional to close out the JIRA when there are over 250 voters and over 125 watchers on this issue.
I hope Atlassian realizes this as a mistake and fix the issue in the Server edition.

Ours either, for a number of reasons. Making that move would either cause us to drop product support renewals for Jira, or move off of the suite entirely.

I hope not, because Jira Cloud is absolutely NOT an option for my organization.

I completely agree with you Robert. Is this the starting trend of no longer supporting the Server product? How difficult would it be to add this feature to the Server product?

I do think that it's kind of silly to just dismiss an issue that has so many votes and watchers :/

It's kind of sad really; of all of the issues I've voted on and watched, they've all received the same response from Atlassian

Atlassian - please reconsider reopening this ticket as this is a HUGE GAPING FLAW in the system.

Hi everyone,

Thanks for voting and commenting on this issue. Filtering for active and inactive users has been available in Atlassian Cloud for some time.

We do not expect that we will re-implement this feature for JIRA Server at any point in the future, therefore we have made the decision to close this issue.

If you are using JIRA Server right now, there are a couple options:

1. You can use the JIRA REST API to return active users, inactive users, or both using the /rest/api/2/user/search resource and the includeActive and includeInactive query paratmers
2. You can query the JIRA database directly as described here

I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.

Regards,
Dave Meyer
dmeyer@atlassian.com
Product Manager, JIRA Platform

We also want this. It's a shame that such a basic feature, which is needed regularly (to check currently active users) is not available and database events have to be created to get a report instead of filtering out inactive users via GUI and then having an option to export the results to an Excel-Sheet or CSV.

We want this too.

It's really painful that such a simple search indicator does not exist. It contains to the user management and with in to your license model, which should weight very heavy for you.

User management is painful - our Active Directory was pulled in on setup (over 50000 accounts) and I can't filter it down to only see active accounts. Please, please, please improve the user management capabilities. I agree with the original requester - this would be very helpful!

Original request description (original description was blank, so let's use one of the duplicates' description for clarity):
I suggest to add another combo box to Filter Users section, which allows filtering the list by users' statuses (all/active/inactive).

@Harvey Moore: that was exactly what I was looking for. (Wish I could "upvote" your response!)Thanks for posting!!

Having just updated our license I noticed that one of the items listed on the "License Information" page is "user limit," but in brackets it tells you how many active users you have. If you are able to do that, then it shouldn't be much of a step to determine which ones are the active ones that have been indetinified.

bberenberg, Thanks for answer.
ecampeanu, Answering your question - it's not possible to build such JQL query. New function to be developed by Atlassian for that.

ecampeanu, this issue is not about filtering in JQL, it is for filtering in the Users list.

@Sergi: please provide the example of a JQL query which will show all the issues with the assignee an inactive user.

Isn't it done? I can filter by active/inactive/all.
At least, in my Cloud JIRA.

Yet again, simple basic functionality overlooked when adding the "Inactive" tick box, but now deemed not important enough to actually work on.

@Thorsten
JRA-32874 looks like a duplicate of this ticket.

What is the difference to JRA-32874?

In Users Management, if Jira allows specifying the criteria Contains/Does Not Contain rather than only supporting Contains, one would then be able to specify Full Name Does Not Contains "[X]" as that is what Jira now shows for disabled users, that is, assuming the directory user filter leaves out disabled accounts. e.g. for Active Directory using User Object Filter:

 (&(objectCategory=person)(sAMAccountName=*)(!(userAccountControl:1.2.840.113556.1.4.803:=2))) 

We have our own instance of Jira and accounts are enabled and disabled through Active Directory. However, Jira admins still have to go into Jira and deactivate terminated accounts by hand. Not a big deal if we stay on top of it every month.
We found that we needed to do more than just deactivate a user. We started adding an asterisk to a user's name so that you could identify an inactive user from an exported report, like Excel. We also needed to add "-term" to the username because Active Directory can reuse a user name after a certain amount of time. So we needed a way to keep the history of that particular user and to allow a new Jane Doe to use "jdoe" for a login.

So we can easily find a list of deactivated users, but we can't get a list of only active users. Would still like to be able to do that-- and to export the list with user activity info so that we can do some clean up and understand who's doing what in Jira. (too bad Google Analytics doesn't work well with Jira).

The reason to keep users is because sometimes you take them out of the group that has a license, but you want all their information to remain because they may be simply not using the product for a while.

@Tobias,
Personally I only see one reason, why it could make sense to keep inactive users in the user list: If they are been used as place holders. Of course it would be also useful, to have them sorted at the end, but that's not the best solution.

And imagine the case, you want to send a notification to all users in a specific group. I think, It doesn't makes sense, to have inactive users considered and sending "e-mail delivery failure" to the Jira admin.

@Jose
Does this not mean that it would be the wrong thing to filter inactive user from this fields?
There might be good reasons to set the value of a user field to an inactive user (like for example the "reporter" field).

Would be sorting inactive user to the end of the list be the better solution?