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

Assignee history (WAS / CHANGED FROM) not searchable by either full name or user name when searching anonymously

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Medium
    • None
    • 4.4.4, 5.0.2, 6.3.8, 8.5.1
    • JQL

    • standalone

    Description

      Original Description

      I have Jira 4.4.4 and Jira 5.0.2 instances, both hooked up to LDAP. I’m trying to find issues where the assignee was a certain person but has now changed. For the sake of example, let’s call this user John Smith.

      I’m using LDAP, so the full name looks like “Smith, John” and the username looks like “jsmith”.

      Both of these queries work:

      assignee = "Smith, John"

      and

      assignee = jsmith

      But if I try

      assignee was jsmith

      I get the error

      The value 'jsmith' does not exist for the field 'assignee'.

      And if I try

      assignee was "Smith, John"

      I get no results!

      The same things happen with “changed from” instead of “was”.

      I thought it might be the comma messing things up, but the same things happen when I use the pair “Jira Admin” and “admin”.

      I found two similar bugs in the database: https://jira.atlassian.com/browse/JRA-26953 and https://jira.atlassian.com/browse/JRA-27717 , but they don’t mention anything about the username not existing error. That’s why I’m filing a new bug. I thought it might be relevant that I’m using LDAP.

      New findings in JIRA 6.3.8

      1. Regarding the username:
        • if searched by someone with Browse Users global permission, results are returned correctly
        • if searched by someone without Browse Users global permission, the following error is thrown:

          This has been discussed in some of the comments below and one workaround is to grant the Browse Users global permission to those who need to perform searches with assignee was <username> frequently
      2. Regarding the fullname:
        • when a new user is created, searching with assignee was <fullname> is not possible, resulting in this error (not depending on Browse Users global permission):
        • however, after assigning an issue to this user, then searching with assignee was <fullname> is possible (not depending on Browse Users global permission)

      Suggestion

      • When a search with username fails, a more meaningful message should be displayed instead of saying that the user does not exist
      • Sometimes, a user without Browse User global permission can still search with username, but this is not easily reproducible
        this may involve some username change or assignee change which can't be reproduced consistently

      Attachments

        1. fullname.png
          fullname.png
          9 kB
        2. username.png
          username.png
          6 kB

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-26953 'WAS' operator does not work with full names in advanced searching

          • Low - Low priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-27717 JQL WAS operator can not search for a username by full name

          • Low - Low priority issues
          • Gathering Impact
          mentioned in

          Page Loading...

          Activity

            People

              Unassigned Unassigned
              cedric zabel CEDRIC ZABEL
              Votes:
              16 Vote for this issue
              Watchers:
              16 Start watching this issue

              Dates

                Created:
                Updated: