I am planning a Jira migration between OnPrem (Server or Data Center) and Cloud. Is there anything I need to do for Timepiece migration?
I am getting "Error: Issue with ID 1685944 was returned from the search but not found on system. Your Jira indexes might be corrupt. Contact your Jira Admin and try reindexing Jira." error
-
This is related to a Jira bug that breaks Jira's data integrity.Sometimes search results become out of sync. In most cases, re-indexing solves the problem, but it is not guaranteed.You might need to take additional actions.In the worst case, you might need to ask Atlassian support about this.
-
In short, Jira returns an issue as part of the search results but when Timepiece asks for the history of that issue, Jira says “I don’t have this issue”.
-
At this point, Timepiece throws an error, because simply ignoring this issue would mean the report results will be inaccurate. Timepiece itself can’t make that decision.
-
Here is what you can do:Quick workaround:Exclude the problematic issues from your Timepiece reports.Get your reports with a custom JQL filter type and use a JQL like “project = ABC and issue not in (1685944)“.This will effectively exclude that issue from your report and work around the problem.Permanent solution:Re-index Jira.If your instance is too large and re-indexing the whole system is too time consuming, you can try to find out which Jira project this issue was in and re-index that project.How to find the issueTry searching for this issue with a JQL like “issue in (1685944)“. If this query returns the issue, you will see the issue's project either by looking at its key or by adding the “project” field as a column to the search results.You can also try finding this issue directly in your Jira DB's "jiraissue" table.If you find the project, then you can re-index just that project, instead of the entire system.