JQL Status was in (status1, satatus2) fails for Team Managed projects

[mini]

I've different projects and using JQL to report progress.

For all project, until now, requesting historical status was working well ,

except for 1where the following request is failing :
Status was in ("To Do","Ready For Dev","In Progress","Done") on ("2021-10-24 00:00")

Projet
Project was created as private (now limited)
Project was created as Team Managed

ticket history confirms stickets were having statuses set at the given date
request with status was not empty returns the list of tickets  !!

was in request with single status or ist of statuses was failing 
request with status was "To Do" returns nothing
request with status was "In Progress" returns nothing
.....

Can you fix this so that jql service can be operational

[Bill Sheboy]

Hi @mini 

There is an open defect for this symptom for team-managed projects, when querying on the default status values: https://jira.atlassian.com/browse/JRACLOUD-77518

Kind regards,
Bill

[mini]

The defect is quite the same

BUT

Opened 2.5 years ago, and still no Fix 
the proposed workaround is not working, and just return inconsistent results

- status was 10500=> 2 results
- status was 11433 => 3 results
- status was in (10500,11433) => 2 results (and only one of the preceeding)

Keep crossing my fingers
so that it might be possible someday to request all historical statuses of all projects
but, it seems that Altassian don't care about fixing it, and just don't assume to say Rejected - Won't Fix 

I used to work with jira from years (15) but could not deal with such impediments, where we can't trust results returned by APIs/JQL...

[Bill Sheboy]

Mini, at this moment the only thing is to watch that defect to note any changes.  Perhaps also consider if there is another way to query what you need without WAS on the status field see if that helps.

[Nic Brough -Adaptavist-]

If the project is "private", the first debugging question is "can the user trying the filter see the issues in the project at all?"

[mini]

the status have been changed to limited and user requesting is able to see and modify issues.

furthermore, we migrated tickets in a company managed project, and they still not appear in JQL queries.

It seems like historical status is managed in an other way...