Operator cannot be applied to moved issue key
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
When running the JQL as shown below, an error occurs stating that "Operator cannot be applied to moved issue key."
1
project = TD and issuekey <= TD-5ERROR:
Environment
9.4.2
Diagnosis
Please review the output of the following database query and replace "problematic_issuekey" with the issue key that is causing an issue. In this example, it is TD-5.:
1
select * from moved_issue_key mik where mik.old_issue_key = '<problematic_issuekey>'Cause
When executing the JQL in Jira, it is crucial to validate the moved issue keys before proceeding. If an issue has been moved, Jira will return "Operator cannot be applied to moved issue key" for the corresponding operator.
Solution
Workaround
Adjust the JQL comparison to avoid using an equals comparison. For example, you could adjust the JQL to use a comparison instead of
1
project = TD AND issuekey < TD-6This can still logically return issues in the TD project before that TD-6 issuekey
Was this helpful?