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

OR statement in JQL with resolutiondate field shows incorrect results.

XMLWordPrintable

      Summary

      When using a JQL filter with the resolutiondate field and an OR statement, JIRA does not retrieve the correct results.

      Example: "resolutiondate = EMPTY OR resolutiondate >= endOfDay(-2)"

       

      Steps to Reproduce

      1. Create a sample software project in the instance
      2. Navigate to Issues > Search for issues
      3. Enter resolutiondate = EMPTY as the JQL
      4. Note the amount of results
      5. Enter resolutiondate >= endOfDay(-2) as the JQL
      6. Note the amount of results
      7. Enter resolutiondate = EMPTY OR resolutiondate >= endOfDay(-2) as the JQL

      Expected Results

      JIRA should show issues from both statements

      Actual Results

      JIRA only shows the issues from the resolutiondate >= endOfDay(-2) part of the JQL query.

            [JRACLOUD-67333] OR statement in JQL with resolutiondate field shows incorrect results.

            Megha added a comment -
            Atlassian Update - October 26, 2020

            Hi everyone,

            Thank you for previously raising this bug and bringing it to our attention.

            Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.

            As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.

            Thank you again for providing valuable feedback to our team!
            Jira Cloud team

            Megha added a comment - Atlassian Update - October 26, 2020 Hi everyone, Thank you for previously raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users. As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know. Thank you again for providing valuable feedback to our team! Jira Cloud team

              Unassigned Unassigned
              ilabras Ibrahim (Inactive)
              Affected customers:
              3 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: