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

JQL 'was in' using Status names returns less issues than when using status ID

      Issue Summary

      The was in JQL function returns fewer issues when using the statuses name as a parameter, than when using the statuses IDs.

      Steps to Reproduce

      1. Compare the results of the two JQLs like in the following example:
        project = <PROJECT_KEY> and status was in ("To Do") on endOfDay(-1) AND type in (Story)
        
        project = DP and status was in (<STATUS_ID>) on endOfDay(-1) AND type in (Story)
        

      Expected Results

      The same amount of issues should be returned

      Actual Results

      There is a discrepancy in the number of issues returned

      Workaround

      Use the status ID instead of its name.

            [JRACLOUD-81443] JQL 'was in' using Status names returns less issues than when using status ID

            Matthew Hunter made changes -
            Resolution New: Timed out [ 10 ]
            Status Original: Gathering Impact [ 12072 ] New: Closed [ 6 ]
            Matthew Hunter made changes -
            Labels Original: jsw-s1 New: jsw-s1 timeout-bulk-close202407
            SET Analytics Bot made changes -
            Support reference count Original: 1 New: 2
            Gerson Gutierrez made changes -
            Labels New: jsw-s1
            SET Analytics Bot made changes -
            Support reference count New: 1
            Brock made changes -
            Status Original: Needs Triage [ 10030 ] New: Gathering Impact [ 12072 ]
            Pablo Albuquerque created issue -

              Unassigned Unassigned
              6c7cdac751c7 Pablo Albuquerque
              Affected customers:
              1 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: