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

Search user properties when searching a user with the user auto-completion functionality

    XMLWordPrintable

Details

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

    Description

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

      The user browser's auto-complete feature is great, but can be even better. I propose improving it (along with a setting) to enable searching users based on their properties. A simple use case could be that we have an additional username (or say why not a phone number) attached to the user as a property. When selecting a user using the auto-complete functionality one would want to be able to use these properties when searching a user.

      Say John Smith (jsmith) has a phone number defined using the property "phoneNumber" with a value "12345". When searching for him using the auto-complete feature, one could use any of the following (the last one being the new feature):
      John
      Smith
      jsm
      123

      This should be relatively easy to implement, as this only requires adding a bit of code to the DefaultUserPickerSearchService's userMatches function. The user object is already fetched so we already have the properties in the object.

      Adding a setting to enable/disable searching these properties would require a bit more coding but would still be fairly trivial to implement.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              790cb4f9dbbe Ivar Ekman
              Votes:
              14 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: