Bug: JIRA Cloud JQL WAS IN DURING () bug! (Different results in server and cloud for some JQL)

[javierdvegu]

I have realized that the was in () JQL search seems to have a bug. In JIRA server performs well as expected so that if I search:

Jira server: returned only the issues that was in in progress during today. Basically the issues I have in progress today.

project = MyProject AND issuetype = TaskType1 and status was "in_progress" DURING (2022-12-26,2022-12-27)

The same search in JIRA Clouds return all the issues that were in a moment on time in in progress state and seems not to take care of the DURING.

So, to sum-up completely different behaviour in JIRA Cloud and JIRA server. JIRA servers seems fine because I only expect to see the issues that were in that state during that time (not that have been before in that past state).

Any info or feedback from atlassian will be appreciated. 

Thanks a lot,

[javierdvegu · Accepted solution]

At the end the solution was contact Atlassian support. In my case they changed or corrected some bug in the instance and the problem was solved.

[Ste Wright]

Hi @javierdvegu 

Just to provide a second point of reference - I tried this with a Company-managed Project and it performed as required.

Team-managed only worked when I used the Status ID, rather than the word itself. You do mention above though that you've tried this.

Given this bug seems to be intermittent, I'd suggest.

• Comment on the relevant Bug on JAC - either JRACLOUD-78540 or JRACLOUD-79741 
• Get help from Atlassian via Atlassian Support

Ste

[javierdvegu]

I have seen this issue:

https://jira.atlassian.com/browse/JRACLOUD-79741

Here it is an image of the search:

first performing the search shows near all of the issues in the project. And the search was for the in progress issues today. More or less same search doing status=in progres (today) shows that today only 5 where aprox in in progress.

Looking at one of the previous list is shows the issue transition out of in progres in october 2022. Doing the same search in Jira server shows correct results. Let's see if it is already solved. I have tried using status id but no luck.

Thanks a lot

[Trudy Claspill]

Hello @javierdvegu 

Welcome to the Atlassian community!

I am not able to replicate your issue in my Jira Cloud environment.

Can you show use the results of the search in List View, showing the Status field? You can obscure any confidential data. If it contains issues you think should not be there, can you show us the status change entries from that issue's History?

[javierdvegu]

I answer in the same thread  but above. Sorry. But it is just above in case you could have a look.

[Trudy Claspill]

Is your project a Company Managed project or a Team Managed project?

I was trying to reproduce in a Company Managed project.

I notice that the issue you found is marked as Closed/Fixed as of Sept. 2022. It also has a linked issue indicating it was cloned from another which is still unresolved.

https://jira.atlassian.com/browse/JRACLOUD-78540

The info in that other issue indicates that they fixed issues with this specifically for Company Managed projects, but there may still be issues when trying to use it for a Team Managed project.

[javierdvegu]

It is company managed project but seems not working properly at least in our jira cloud environment.

[javierdvegu]

The same issues seems to happen when lookint to assignee was in .... Seems in our cloud at least it is not possible to search for issues assigned to a user during the past which is key for KPIs staff. 

[Trudy Claspill]

I encourage you to open a support case directly with Atlassian Support to investigate this issue more.

https://support.atlassian.com/contact/#/

And please post back here with the information/solution you get.