Inconsistence in JQL searches towards resolution

XMLWordPrintable

    • 4
    • Severity 3 - Minor
    • 0

      Summary

      There is inconsistence in the results when performing JQL searches based on the Resolution.

      Tests

      • Example #1: issue AP-10 - Unresolved; issue AP-1 - Unresolved (but had a resolution set at some point):
        • Search #1: resolution is EMPTY AND project = AP -> No issue returned
        • Search #2: resolution = unresolved AND project = AP -> No issue returned
        • Search #3: resolution WAS unresolved AND project = AP -> No issue returned
        • resolution #4: resolution WAS EMPTY AND project = AP -> Issue AP-1 returned

      There may be different results in different Jira instances. I was not able to match results between my test instance and a teammate's one, for example.

      Environment

      Jira Cloud

      Expected Results

      Search #1: should return AP-10.
      Search #2: should return AP-10.
      Search #3: if Search #4 returned AP-1, this one should have returned AP-1 as well.

      Actual Results

      • Search #1: No issue returned
      • Search #2: No issue returned
      • Search #3: No issue returned

      Workaround

      No workaround at the moment

            Assignee:
            Unassigned
            Reporter:
            Leonardo De Almeida
            Votes:
            6 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: