• Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? 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).

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

            I would like to echo what @stephanie said - I get the same error for Jira Cloud.

            My very basic query: resolution = Unresolved AND assignee in (inactive-users). The result is:

            The value 'inactive-users' does not exist for the field 'assignee'.

            Charles S. added a comment - I would like to echo what @stephanie said - I get the same error for Jira Cloud. My very basic query:  resolution = Unresolved AND assignee in (inactive-users).  The result is: The value 'inactive-users' does not exist for the field 'assignee'.

            I get an error that says The value 'inactive-users' does not exist for the field 'assignee'.

             

            This is my query: project = BO AND resolved >= -7d AND assignee not in (inactive-users) 

            Stephanie Willis added a comment - I get an error that says The value 'inactive-users' does not exist for the field 'assignee'.   This is my query: project = BO AND resolved >= -7d AND assignee not in (inactive-users) 

            @stephanie among other thing to do a simple query to return assignees and reporters who are inactive ( JQL like " assignee IN (inactive-users) or reporter IN (inactive-users)

             

            Alejandro Iglesias added a comment - @stephanie among other thing to do a simple query to return assignees and reporters who are inactive ( JQL like " assignee IN (inactive-users) or reporter IN (inactive-users)  

            I do not understand how I use this filter on Jira Cloud. Can someone please explain to me? 

            Stephanie Willis added a comment - I do not understand how I use this filter on Jira Cloud. Can someone please explain to me? 

            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:
              138 Start watching this issue

                Created:
                Updated:
                Resolved: