• We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Atlassian Update – 4 January 2016

      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

      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).

            [JRASERVER-29149] Filter out inactive users in the Users list

            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.

             

            Tibor Tasi [Everit] added a comment - 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.  

            Tom Keidar added a comment -

            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.

            Tom Keidar added a comment - 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.

            Simon Hedges added a comment - - edited

            The proposed solution does not resolve the issue.  The issue is about filtering out inactive users in the user list.  Whereas the SQL provided is a potentially useful workaround, it is a workaround, and not a fix.  Please re-open this ticket.

            Furthermore the whole user licensing reporting in the Atlassian toolset is a mess:  there are inconsistencies and bugs in a system that has hard limits on licensing.  Please Atlassian, sort out this ticket, and also make your tools consistent and for those using Crowd, enable a 1 stop shop for licence reporting for all those tools managed by Crowd.

            Simon Hedges added a comment - - edited The proposed solution does not resolve the issue.  The issue is about filtering out inactive users in the user list.  Whereas the SQL provided is a potentially useful workaround, it is a workaround, and not a fix.  Please re-open this ticket. Furthermore the whole user licensing reporting in the Atlassian toolset is a mess:  there are inconsistencies and bugs in a system that has hard limits on licensing.  Please Atlassian, sort out this ticket, and also make your tools consistent and for those using Crowd, enable a 1 stop shop for licence reporting for all those tools managed by Crowd.

            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.

            Michael Evans added a comment - 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).

            Boris Berenberg - Atlas Authority added a comment - 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).

            Rob Horan added a comment -

            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.

            Rob Horan added a comment - 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

            Naresh Mareedu added a comment - @Boris Berenberg, I have replied

            Thank you feedback1534286591!

            kitkat (Inactive) added a comment - Thank you feedback1534286591 !

            nmareedu1585045417, I just sent you an email

            Boris Berenberg - Atlas Authority added a comment - 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.

            Naresh Mareedu added a comment - @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.

              Unassigned Unassigned
              0e91e160c154 Yossi Zinger
              Votes:
              264 Vote for this issue
              Watchers:
              145 Start watching this issue

                Created:
                Updated:
                Resolved: