---
title: "Troubleshooting: CMJ snapshot deployment blocked by missing Jira Toolkit searchers"
canonical: "https://support.appfire.com/space/SUPPORT/3644456963/Troubleshooting%3A%20CMJ%20snapshot%20deployment%20blocked%20by%20missing%20Jira%20Toolkit%20searchers"
format: markdown
---
## Summary

During a Jira Data Center upgrade (for example, from 10.x to 11.x), deploying a **Configuration Manager for Jira (CMJ)** snapshot may be blocked due to missing custom field searchers from the **Jira Toolkit** app. This occurs because newer versions of Jira Toolkit (v3.0.0+) have removed or renamed certain searchers that were present in older versions (v2.0.0), and CMJ 9.0.2+ treats these missing references as hard blockers to ensure configuration integrity.

## Symptoms

When attempting to deploy a snapshot to a target instance, the deployment process halts with an error indicating that specific Jira Toolkit fields or searchers are missing. Common searchers identified in this issue include:

- **Multi Issue Key Searcher**
- **Originating Threat**

The error message typically advises verifying that the add-on versions match between the source and destination instances.

## Error screenshot

![image-20260910-131422.png](media://e49f22a9-4b3e-4b27-be6f-bf4cdc7d1471)


## Cause

1. **App version discrepancy:** The source instance uses an older version of Jira Toolkit (for example, 2.0.0) where these searchers exist, while the target instance uses a newer version (for example, 3.0.0) where they have been removed.
2. **CMJ behavior change:** In CMJ 9.0.2 and later, missing plugin references that were previously flagged as warnings are now treated as **hard blockers** to prevent broken configurations on the target instance.
3. **Limited SPI support:** Jira Toolkit has limited CMJ support and does not implement Appfire's SPI for full migration compatibility, leading to these reference mismatches during major version jumps.

## Resolution

To resolve this, you must recreate the CMJ snapshot on the source instance without the problematic Jira Toolkit references.

### Step-by-step workaround

1. **Disable Jira Toolkit on source:**  
Navigate to **Administration > Manage apps** on your source Jira instance (for example, Jira 10.3.11) and temporarily disable the **Jira Toolkit** app.
2. **Verify configurations:**  
Confirm that no active project configurations or critical workflows are strictly dependent on these specific Toolkit custom fields for the duration of the snapshot creation.
3. **Perform a full reindex:**  
Run a full Jira reindex on the source instance to ensure the search index is updated and no longer references the disabled searchers.
4. **Generate a new snapshot:**  
Create a new CMJ snapshot. Because the app is disabled, the snapshot will not capture the missing Toolkit field searcher references.
5. **Deploy to target:**  
Upload and deploy the new snapshot to your target environment (for example, Jira 11.3.10 with CMJ 9.0.2-jira11).
6. **Re-enable Jira Toolkit:**  
Once the deployment is successfully completed, re-enable the Jira Toolkit app on both the source and target instances.