JQL Queries return different results after migration from Jira Server to Cloud

[Jason Finan]

I need to run some reports for a project which was migrated to the cloud in the middle of 2024. The query is as follows:

project = "XXXX" AND issuetype = Defect AND status WAS "Transferred" ON "2024-01-01" ORDER BY created DESC

When I run this query in the cloud, I get over 8k results which is incorrect however when I run the query in Jira server I get the correct number of issues (around 300)

I am wondering if this is a known issue when a project is migrated, or am I missing something in my query? I'm concerned that we wont be able to run queries and generate reports for projects that were migrated which would be a big problem for us. 

[Sunny Ape · Accepted solution]

Hello @Jason Finan 

There are well-known problems that can arise with JQL when doing status change searches with historical changelogs in Issues imported from a migration.

Refer to these Bugs in JAC, then contact Atlassian directly for assistance:

• JRACLOUD-76991 - Some historical JQL searches return additional issues
• JRACLOUD-70797 - JQL query search using "status was" returns incorrect unreliable results

[Jason Finan]

Thanks David for the steer. I'll check out the known bugs and contact support if needed. 

[Vishal Biyani]

@Jason Finan 

are all the changelogs imported correctly?

Can you spot check (for few issues) statusCategoryChangedDate column value in server and cloud and their changelogs to see if you can spot some differences?

[Jason Finan]

I can see from the history of the issues that the status change has been migrated to the cloud correctly and matches server.