We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-79741

JQL query search using "status was" returns incorrect unreliable results for Company Managed projects

      Summary

      For company managed projects, when searching for issues using JQL such as:

      project = PROJECT_NAME AND (status CHANGED FROM "To Do" OR status = "To Do")
      
      status was "In Progress" after "2022-03-09" AND status in ("Ready for Release", Done, Closed, Declined, Postponed)
      
      status was "In Progress" after endOfDay(-21d) AND status in ("Ready for Release", Done, Closed, Declined, Postponed)
      
      assignee WAS currentUser() AFTER "2022-01-01" AND project = "DEMO"
      

      If JQL contains "WAS" and AFTER or endOfDay it ** does not consider the timeline and returns all results.

      The results are unreliable.

      Steps to Reproduce

      • Work case 1
      1. Create a  project with statuses "To Do", "In Progress" and "Done".
      2. Create some issues, and transition some of them around.
      3. Run the query: project = PROJECT_NAME AND (status CHANGED FROM "To Do" OR status = "To Do")
      4.  Run the query  status was "In Progress" after endOfDay(-2d) 
      • Work case 2
      1. Have or create several issues in and outside of the required parameters 
      2. Run the query status was "In Progress" after endOfDay(-21d) AND status in ("Ready for Release", Done, Closed, Declined, Postponed)

      Expected Results

      • Only issues in the specified parameters should be returned.

      Actual Results

      • Issues not in the specified parameters are returned

      Notes

      We primarily see this happening in these scenarios:

      • The search doesn't work well in company-managed projects when there has been a workflow change

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Jira Platform Cloud'
            1. Jira Platform Cloud
            2. JRACLOUD-79741

            JQL query search using "status was" returns incorrect unreliable results for Company Managed projects

                Summary

                For company managed projects, when searching for issues using JQL such as:

                project = PROJECT_NAME AND (status CHANGED FROM "To Do" OR status = "To Do")
                
                status was "In Progress" after "2022-03-09" AND status in ("Ready for Release", Done, Closed, Declined, Postponed)
                
                status was "In Progress" after endOfDay(-21d) AND status in ("Ready for Release", Done, Closed, Declined, Postponed)
                
                assignee WAS currentUser() AFTER "2022-01-01" AND project = "DEMO"
                

                If JQL contains "WAS" and AFTER or endOfDay it ** does not consider the timeline and returns all results.

                The results are unreliable.

                Steps to Reproduce

                • Work case 1
                1. Create a  project with statuses "To Do", "In Progress" and "Done".
                2. Create some issues, and transition some of them around.
                3. Run the query: project = PROJECT_NAME AND (status CHANGED FROM "To Do" OR status = "To Do")
                4.  Run the query  status was "In Progress" after endOfDay(-2d) 
                • Work case 2
                1. Have or create several issues in and outside of the required parameters 
                2. Run the query status was "In Progress" after endOfDay(-21d) AND status in ("Ready for Release", Done, Closed, Declined, Postponed)

                Expected Results

                • Only issues in the specified parameters should be returned.

                Actual Results

                • Issues not in the specified parameters are returned

                Notes

                We primarily see this happening in these scenarios:

                • The search doesn't work well in company-managed projects when there has been a workflow change

                        pswiecicki Piotr Swiecicki
                        mtokar Michael Tokar
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        14 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            pswiecicki Piotr Swiecicki
                            mtokar Michael Tokar
                            Affected customers:
                            0 This affects my team
                            Watchers:
                            14 Start watching this issue

                              Created:
                              Updated:
                              Resolved: