Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-30412

[User-Picker CF] this field should not fetch inactive users.

XMLWordPrintable

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

      Hi,

      Currently, User-Picker field fetches all users including in-active ones. What is the use case in fetching inactive users?

      I think the API should fetch active users only or its behaviour should be in align with 'Assignee' field.

      Regards,
      Dipti Ranjan Behera

      Steps to Replicate

      1. Create an User Picker custom field in a system with inactive users.
      2. Click on the 'Select a user' icon ().
      3. A pop up opens displaying all the users, including inactive ones (URL: http://<JIRA_SERVER>/secure/popups/UserPickerBrowser.jspa?formName=jiraform&multiSelect=false&decorator=popup&element=customfield_<CF_ID>).

      Expected Results

      Only the active users should be displayed - or it should be possible to at least filter inactive users out.

        1. browse_users.png
          browse_users.png
          4 kB

            [JRASERVER-30412] [User-Picker CF] this field should not fetch inactive users.

            systems-intern added a comment -

            Jira is a ticketing system and with this use case often comes requirements for audits and the retention of historical data to demonstrate processes/procedures. How can you disable the selection of inactive users in such a case and thus prevent tickets from being processed? We now have to remove users, and this completely distorts the history, for example for permission tickets in the helpdesk project. This prevents the documentation of rights assignment or exit processes. I guess some companies use service desk projects for employee departures. Here you will almost always run into the problem with deactivated users, because you don't collect them in the user directory forever. Has any thought been given to this?

            systems-intern added a comment - Jira is a ticketing system and with this use case often comes requirements for audits and the retention of historical data to demonstrate processes/procedures. How can you disable the selection of inactive users in such a case and thus prevent tickets from being processed? We now have to remove users, and this completely distorts the history, for example for permission tickets in the helpdesk project. This prevents the documentation of rights assignment or exit processes. I guess some companies use service desk projects for employee departures. Here you will almost always run into the problem with deactivated users, because you don't collect them in the user directory forever. Has any thought been given to this?

            jacqueline.meister@plusserver.com added a comment -

            But i cant edit tickets where an inactive user is choosen in any user picker field anymore, because i cant save the issue and get the error that i cant choose that user in that field...so we cant edit older issues and keep historical data. This is stupid >_<

            jacqueline.meister@plusserver.com added a comment - But i cant edit tickets where an inactive user is choosen in any user picker field anymore, because i cant save the issue and get the error that i cant choose that user in that field...so we cant edit older issues and keep historical data. This is stupid >_<

            Jurij Vidmar added a comment -

            The issue does not seem to be as severe as the previous post suggests. It seems that autocomplete for inactive users no longer works, but these users can still be queried. So JQL ...

            reporter = username

            or

            reporter = "Full Name"

            ... still works, but you have to know either the person's username or full name. I agree though that even lack of autocomplete is an issue, especially for organizations with many users. Not sure if the decision to filter out users is the best one. A good UI indicating a user as inactive would be better. Deleted users get a trailing (X) which is simple and helpful. Why are inactive users treated differently?

             

            Can someone from the Jira team comment on this since it's a recent regression?

             

            Jurij Vidmar added a comment - The issue does not seem to be as severe as the previous post suggests. It seems that autocomplete for inactive users no longer works, but these users can still be queried. So JQL ... reporter = username or reporter = "Full Name" ... still works, but you have to know either the person's username or full name. I agree though that even lack of autocomplete is an issue, especially for organizations with many users. Not sure if the decision to filter out users is the best one. A good UI indicating a user as inactive would be better. Deleted users get a trailing (X) which is simple and helpful. Why are inactive users treated differently?   Can someone from the Jira team comment on this since it's a recent regression?  

            confluence@ecogood.org added a comment -

            This was implemented without thinking unfortunately.

            I agree that it should not be possible to assign a ticket to an inactive user.

            But did anyone think about searching for tickets?
            You removed the option to search for tickets, that were

            • created
            • modified
            • solved
            • commented
            • ... etc.

            by an inactive user.

            And this after sleeping 2 years? Unbelievable

             

            confluence@ecogood.org added a comment - This was implemented without thinking unfortunately. I agree that it should not be possible to assign a ticket to an inactive user. But did anyone think about searching for tickets? You removed the option to search for tickets, that were created modified solved commented ... etc. by an inactive user. And this after sleeping 2 years? Unbelievable  

            Alper added a comment -

            I am setting up a service desk where people can request access for applications. Within the company, all usernames must be equal to the active directory.
            Not all users have access to JIRA. Now as far as I can tell, active users in the active directory, are considered inactive in JIRA if they do not use JIRA. Is it possible to disable this filter, and include it as an option?

            Alper added a comment - I am setting up a service desk where people can request access for applications. Within the company, all usernames must be equal to the active directory. Not all users have access to JIRA. Now as far as I can tell, active users in the active directory, are considered inactive in JIRA if they do not use JIRA. Is it possible to disable this filter, and include it as an option?

            Sstack added a comment -

            Agreed. User Picker should exclude inactive users.
            Atlassian, please indicate fixing this issue is on your radar please. Thank you.

            Sstack added a comment - Agreed. User Picker should exclude inactive users. Atlassian, please indicate fixing this issue is on your radar please. Thank you.

            Dipti Ranjan Behera added a comment -

            Is there any time-period in which it will be implemented?

            Dipti Ranjan Behera added a comment - Is there any time-period in which it will be implemented?

              Unassigned Unassigned
              437ea89af607 Dipti Ranjan Behera
              Votes:
              1 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: