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

JQL query search using "status" returns incorrect unreliable results

    XMLWordPrintable

Details

    Description

      Summary

      When searching for issues using a "status" statements ("status was", "status =", "status changed"), the results are unreliable. This happens if there is a Next-gen project in the Jira's Cloud instance.

      Steps to Reproduce

      1. Search for issues using a "status was in/was not in (status1, status2) on date" argument;

      Expected Results

      • All the issues that were on that statuses on that date returns as result of the query.

      Actual Results

      • Some issues show in the result of the query. Other that also matches the argument, don't.

      Update on April the 17th, 2020!

      This problem is very consistent on issues that are imported through a .CSV file and are on a different status than the query.

      Workaround(s)

      Attachments

        1. JRACLOUD-70797-1.png
          JRACLOUD-70797-1.png
          100 kB
        2. JRACLOUD-70797-2.png
          JRACLOUD-70797-2.png
          151 kB
        3. JRACLOUD-70797-3.png
          JRACLOUD-70797-3.png
          117 kB
        4. JRACLOUD-70797-4.png
          JRACLOUD-70797-4.png
          424 kB

        Issue Links

          Activity

            People

              Unassigned Unassigned
              rgebhardt@atlassian.com Ricardo Gebhardt (Inactive)
              Votes:
              27 Vote for this issue
              Watchers:
              43 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: