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

Basic Search default Boolean inside a Group is incorrectly mapped to "+" operator

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Medium
    • None
    • 7.0.0, 8.0.0, 7.13.5, 8.2.4
    • Navigation - Search
    • None

    Description

      Issue Summary

      Please Note the current Documentation Inconsistency BUG about the expected default behavior when a Boolean is used:

      Clarification Reference from Basic Search documentation found here: "Search syntax for text fields", Noting that the expected default behavior of not using a boolean value between two terms is the "AND" operator not the "OR" operator as both variations are currently listed in the document and the following statement is true:

      "If you combine multiple terms without specifying any Boolean operators, they will be joined using AND operators."

      However when doing a Query that has two terms missing an Operator nested inside a Group the behavior defaults to a "+" rather than an "AND"
      EXE using a very simple text search:
      in the Text field search for test (singleTerm OR term OR compound word) noting that compound word is actually two separate terms where Term 1 = "compound" and term 2 = "word" per definition criteria of a Term:

      There are two types of terms: single terms (e.g. "hello") and phrases (e.g. "hello dolly")

      This would be consider a Phrase if placed in quotes, as there are no quotes the default conjunction operator should be "AND" however we are seeing behavior similar to the "+" Operator unless explicitly flagged as "AND" or as "OR" in the query.

      Environment

      Cloud & Server affected Tested and verified behavior on current Cloud version and server version in the range 7.2, 7.13, 8.0, & 8.2

      If using Jira cloud See corresponding Cloud bug Report here: https://jira.atlassian.com/browse/JRACLOUD-72542

      Steps to Reproduce

      1. Create Requests containing only one of the following in each issues Description and any other combination that you want to verify against:

        test word
        test compound test word

      2. Run the search using Control search
        test (singleTerm OR term OR compound word)
        

        #run the search using verification search

        test (singleTerm OR term OR compound AND word)
        test (singleTerm OR term OR compound + word)
        

      Expected Results

      Expected that control query test (singleTerm OR term OR compound word) and the "AND" test query test (singleTerm OR term OR compound AND word) would return the same result set which would be the issue containing "test compound test word"

      Actual Results

      both text combinations are returned and this is the same result set as the "+" operator test query

      Notes

      It appears to be a conflict of the double AND application on the distributive action to the nested query inside the (grouping), as the portion "test()" is technically triggering the default conjunction operator as a "test AND ()" with the additional distribution of the alternate default conjunction operator portion "AND word" making it "test AND AND word" causing some conflict in logic at this point,

      As an additional visual exe manual distribution of operators in the string test (singleTerm OR term OR compound word) to a advanced query should look like this:

      text ~ (test AND single term) OR (test AND term) OR (test AND compound) AND (test AND word)
      

      BUT is actually being treated as:

      text ~ (test AND single term) OR (test AND term) OR ((test AND compound) AND (test AND word))
      

      OR

      text ~ (test AND single term) OR (test AND term) OR (test AND compound) + (test AND word)
      

      Workaround

      First NOTE the "AND" is expected not the "OR" per the linked documentation BUG, so use the "AND" operator variable Manually rather than relying on the query to use a whitespace to default to the default conjunction operator "AND" especially when used in nested queries to verify the correct search operator is being used.
      OR
      Rely on Advanced Search queries as defined in:

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              emccutcheon Earl McCutcheon
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated: