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

Advance Search for String that Contain Hyphen Returns Result

      When using Advance Searching, searching for a string that had hyphen in between return result. Expected no result is returned since it is not a complete string (whole word)

      Quote from the documentation for text searching:

      Whole words only

      JIRA cannot search for issues containing parts of words but on whole words only. The exception to this are words which are stemmed.

      This limitation can also be overcome using fuzzy searches.

      Steps to replicate:

      1. Create an issue test-test on summary
      2. Search for "summary ~ test" returned the result test-test created earlier (Not expected)
      3. Create another issue test-test123 on summary
      4. Search for "summary ~ test123" returned no result (Expected)

            [JRASERVER-33306] Advance Search for String that Contain Hyphen Returns Result

            Ian Mayoh added a comment -

            There have been issued raised of a similar vein. See https://jira.atlassian.com/browse/JRA-6218.

            Ian Mayoh added a comment - There have been issued raised of a similar vein. See https://jira.atlassian.com/browse/JRA-6218 .

            Ian Mayoh added a comment - - edited

            I raised this in the first place. It may not have been reported but that doesn't mean that people aren't just putting up with it and muttering away under their breath and having to find some inconvenient way around it. It is an easy thing to cause problems. I am relying on users to enter data and putting a space between a hyphen or a colon and a string. it is such a simple slip that makes the string unsearchable. As I said in the support call that spawned this issue, software should work as users expect. Users (me included) expect that a string search is exactly that, i.e. if I search for any sequence of chars it will be found, and not that they have to include the start of the string for a string to be found and have to think about the fact that someone may have missed the space before the string, making it unsearchable.

            Ian Mayoh added a comment - - edited I raised this in the first place. It may not have been reported but that doesn't mean that people aren't just putting up with it and muttering away under their breath and having to find some inconvenient way around it. It is an easy thing to cause problems. I am relying on users to enter data and putting a space between a hyphen or a colon and a string. it is such a simple slip that makes the string unsearchable. As I said in the support call that spawned this issue, software should work as users expect. Users (me included) expect that a string search is exactly that, i.e. if I search for any sequence of chars it will be found, and not that they have to include the start of the string for a string to be found and have to think about the fact that someone may have missed the space before the string, making it unsearchable.

            This has been around for as long as JIRA has had search and I couldn't find another reported bug about it. Additionally there have been no customers reporting this, so I'm just going to close it.

            Eric Dalgliesh added a comment - This has been around for as long as JIRA has had search and I couldn't find another reported bug about it. Additionally there have been no customers reporting this, so I'm just going to close it.

              Unassigned Unassigned
              rgee Richie Gee (Inactive)
              Affected customers:
              0 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: