---
title: "Restored Sprint Data Mismatch After Snapshot Deployment"
canonical: "https://support.appfire.com/space/SUPPORT/2243888295/Restored%20Sprint%20Data%20Mismatch%20After%20Snapshot%20Deployment"
format: markdown
---
### Problem

After deploying a snapshot using Configuration Manager for Jira (CMJ), the restored **sprint data (e.g., sprint names, dates, or states)** does **not match** the original state in the source instance. Users notice inconsistencies in sprint boards or unexpected differences in board configuration, especially when Agile data is involved.

### Cause

This issue occurs due to known limitations in how **Agile boards and sprints** are stored and restored during project snapshot deployment. CMJ only stores certain parts of the sprint metadata. Specifically:

- **Sprint activation timestamps** (e.g., `ACTIVATED_DATE`) are not exported in snapshots.
- Only the **sprint start date** is preserved.
- If Agile boards reference sprints that were updated or deleted outside the scope of the snapshot, discrepancies can arise.

### Symptoms

- Sprint names look similar but are duplicated or differ slightly.
- Start and end dates mismatch.
- Sprint IDs don’t match between source and target.
- Agile boards may show unexpected or missing sprints after restore.

### Diagnosis

1. Compare the **original sprint data** (from the source Jira) and the **restored sprint data** (from the target) in the `AO_60DB71_SPRINT` table.
2. Run this SQL on both source and target:
3. Note discrepancies in `START_DATE`, `ACTIVATED_DATE`, `SEQUENCE`, etc.

### Resolution

#### Step 1: Manually Review and Update Sprint Status

Navigate to **Jira Settings → Issues → Sprints** and:

- Identify sprints incorrectly marked as active.
- Manually close or complete them as needed.

#### Step 2: Rename Sprints (if necessary)

You can rename sprints using:

- **Agile board settings** in Jira.
- **Jira REST API**:
  Include the correct name in the body of the request.

#### Step 3 (Recommended): Preserve ID Mappings for Future Deployments

To avoid similar issues in future deployments:

1. Go to **CMJ → General Settings**.
2. Enable: **“Persist deployed snapshot to current system native ID mappings”**

This ensures sprint and board IDs are mapped correctly between environments.