Details

    • Feedback Policy:

      JIRA feedback is collected from a number of different sources and is evaluated when planning the product roadmap. If you would like to know more about how JIRA Product Management uses customer input during the planning process, please see our post on Atlassian Answers.

      Description

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

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                yossiz Yossi Zinger
              • Votes:
                264 Vote for this issue
                Watchers:
                135 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: