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

XMLWordPrintable

      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

            Bill Sheboy added a comment -

            Greetings!

            This defect seems to be another consequence of the design choices for team-managed projects and that JQL does not appear to limit scope of the query clauses to the projects involved.  There are certainly other open defects and "suggestions" for this symptom, so perhaps link this one to those and mark it as "duplicate" rather than timing it out.  Thank you.

            Kind regards,
            Bill

            Bill Sheboy added a comment - Greetings! This defect seems to be another consequence of the design choices for team-managed projects and that JQL does not appear to limit scope of the query clauses to the projects involved.  There are certainly other open defects and "suggestions" for this symptom, so perhaps link this one to those and mark it as "duplicate" rather than timing it out.  Thank you. Kind regards, Bill

            Matthew Hunter added a comment -
            Atlassian Update - July 11, 2024

            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

            Matthew Hunter added a comment - Atlassian Update - July 11, 2024 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
              6c7cdac751c7 Pablo Albuquerque
              Affected customers:
              1 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: