Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JRACLOUD-67419

JQL equals to Empty is returning incorrect results when combining with other conditions

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Low Low
    • Issue - Navigation
    • None

      Summary

      In some instances, operator = Empty is broken when combining with other condition, for example: JQL resolutiondate = EMPTY OR resolutiondate >= -30d is returning incorrect results. The results will be less than JQL resolutiondate = EMPTY

      Steps to Reproduce

      1. Go to Issue Navigator
      2. Type the following JQL: resolutiondate = empty
        Please take note the number of records returned.
      3. Next, combine the JQL above with other condition, for example: resolutiondate = empty OR resolutiondate >= "-30d"
        Please take note the number of records returned.

      Expected Results

      The results will be the OR of both conditions

      Actual Results

      The number of records that is returned is actually less than the JQL resolutiondate = empty alone. In this case: resolutiondate = empty OR resolutiondate >= "-30d" returns less number of records than resolutiondate = empty

      Workaround

      Modify = empty to use is empty instead

      Additional Notes

      resolutiondate = EMPTY works!
      resolutiondate is EMPTY works!
      resolutiondate is EMPTY OR resolutiondate >= -30d works!
      resolutiondate = EMPTY OR resolutiondate >= -30d returns incorrect results!

            Unassigned Unassigned
            rjustin Ryan Justin (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: