In order to test this,

      1. create a custom field type : Text
      2. create an issue and add alphanumeric values to the custom field (for example, I added bh_ab123,bh_abc,bh12aaa,BH_AGENT)
      3. try searching by "Device name" ~ 'bh*' you get the output with all Device name values
      4. try searching with "Device name" ~ 'bh_*' you will get only one value : bh_ab123

        1. fls-without-star.jpg
          fls-without-star.jpg
          135 kB
        2. fls-with-star.jpg
          fls-with-star.jpg
          115 kB
        3. Screen shot 2013-04-04 at 1.03.41 PM.png
          Screen shot 2013-04-04 at 1.03.41 PM.png
          68 kB
        4. Screen shot 2013-04-04 at 1.05.20 PM.png
          Screen shot 2013-04-04 at 1.05.20 PM.png
          40 kB

            [JRASERVER-32441] Searching with * only searches for alphanumeric characters

            ChrisA added a comment -

            Possibly this is happening when lucene sees a word that has only letters in it and treats it as a word, but when there is a mixture of letters and numbers it treats it as a string, such as a serial number. This may explain the behaviour.

            ChrisA added a comment - Possibly this is happening when lucene sees a word that has only letters in it and treats it as a word, but when there is a mixture of letters and numbers it treats it as a string, such as a serial number. This may explain the behaviour.

            Ruchi Tandon added a comment - - edited

            Adding more screenshots as the customer has provided more scenarios where the problem occurs.

            As you can see when you search with FLS*, it is only returning the results where the part after "FLS" has alphanumeric text.

            Ruchi Tandon added a comment - - edited Adding more screenshots as the customer has provided more scenarios where the problem occurs. As you can see when you search with FLS*, it is only returning the results where the part after "FLS" has alphanumeric text.

            ChrisA added a comment -

            This is because the underscore is treated the same as a space - bh_123 is the same as having two words, 'bh' and '123' to JQL. So the search for bh* is looking for words with bh and another character after it - which doesn't exist.

            ChrisA added a comment - This is because the underscore is treated the same as a space - bh_123 is the same as having two words, 'bh' and '123' to JQL. So the search for bh* is looking for words with bh and another character after it - which doesn't exist.

              Unassigned Unassigned
              rtandon@atlassian.com Ruchi Tandon
              Affected customers:
              3 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated: