---
title: "Troubleshooting BigPicture Iteration Status After Jira Sprint Closure"
canonical: "https://support.appfire.com/space/SUPPORT/3675127834/Troubleshooting%20BigPicture%20Iteration%20Status%20After%20Jira%20Sprint%20Closure"
format: markdown
---
**Internal support guide.** Use this article when an automatically managed, sprint-based BigPicture Iteration remains **In Progress** after its related Jira sprint has been closed.
# Problem
With automatic sprint-based timeboxes enabled, BigPicture Iteration boxes are expected to follow the lifecycle of their corresponding Jira sprints. When the Jira sprint is closed, the linked Iteration should update to **Closed**. Manual status changes are intentionally blocked while automatic management is enabled.
# Symptoms
- An older Iteration box remains **In Progress** even though its end date is in the past.
- Attempting to close the Iteration manually from the BigPicture Overview module displays a validation message stating that the status cannot be updated while automatic sprint-based timeboxes are enabled.
- The roadmap or leadership views continue to show historical iterations as active.
- The related Jira sprint may already be closed, but BigPicture has not reflected the change.
# Prerequisites
- Access to the affected Jira project and board.
- Permission to view sprint details and confirm the sprint lifecycle in Jira.
- Access to the affected BigPicture Box and its Overview or Gantt module.
- Permission to trigger a BigPicture refresh or resynchronization.
# Expected behavior
> ✅ When automatic sprint-based timeboxes are enabled, the Iteration status is driven by the corresponding Jira sprint. Manual status changes in BigPicture are blocked to preserve consistency between Jira and BigPicture.
An end date in the past does not, by itself, confirm that the Jira sprint has been closed. The sprint must be fully closed in Jira, and the status change must successfully synchronize to BigPicture.
# Troubleshooting procedure
## Step 1: Confirm that the Iteration is automatically managed
Open the affected Box configuration and verify that automatic sprint-based timeboxes or auto-managed sprints are enabled.
**Expected result:** The Iteration is linked to a Jira sprint and its status is controlled by the Jira sprint lifecycle.
> ⚠️ Do not attempt to force the status to **Closed** from BigPicture while automatic management is enabled. The validation error is expected and indicates that manual updates are restricted.
## Step 2: Confirm that the Jira sprint is fully closed
Open the Jira board associated with the BigPicture Box and inspect the sprint in the board's sprint list or sprint-management view.
- Confirm that the sprint is marked **Closed**, not merely past its planned end date.
- Confirm that the affected Iteration is linked to the correct Jira sprint.
- Check whether the sprint was closed on the expected board and project.
**Expected result:** Jira shows the corresponding sprint as fully closed.
## Step 3: Resynchronize the affected BigPicture data
In the affected BigPicture Box, open the Overview or Gantt module and use the available **Resynchronize** or **Refresh** action.
Allow the operation to complete, then reopen or refresh the Iteration details.
**Expected result:** BigPicture retrieves the current Jira sprint state and updates the linked Iteration to **Closed**.
## Step 4: Check the Jira board connection
If the Iteration remains In Progress, verify that the Box is connected to the Jira board where the sprint was closed.
- Confirm that the board reference has not changed.
- Check that the integration can read sprint data from Jira.
- Review Jira and BigPicture permissions for the user or service account performing synchronization.
- Check for configuration or integration errors that could prevent sprint data from being imported.
**Expected result:** The connected board is correct, accessible, and able to provide the sprint's current status.
## Step 5: Review task-planning and synchronization conditions
Check whether tasks are being planned to a Box with a sub-scope, such as an Iteration, that is synchronized with a closed Jira sprint. BigPicture may prevent planning tasks into such a Box to avoid warnings or inconsistencies during a subsequent synchronization.
Review recent planning changes and determine whether a failed or incomplete synchronization occurred after the sprint was closed.
# Verification
1. Confirm the related Jira sprint is displayed as **Closed**.
2. Run a manual BigPicture refresh or resynchronization.
3. Confirm that the linked Iteration status is now **Closed**.
4. Refresh the roadmap, Overview, or leadership view and verify that the historical Iteration no longer appears active.
5. Confirm that no new synchronization or permission errors are reported.
# Resolution guidance
> ✅ No additional auto-close configuration is required. When the Jira sprint is correctly closed and synchronization is working, BigPicture should update the linked Iteration automatically.
If the status does not update after confirming the Jira sprint state and running a resynchronization, collect the affected Box, Jira board, Iteration, and sprint details for further investigation.
# Escalation information to collect
- BigPicture Box name and URL, if available.
- Jira project and board name.
- Affected Iteration name or identifier.
- Related Jira sprint name or identifier.
- Confirmation that the sprint is fully closed in Jira.
- Time and result of the most recent BigPicture resynchronization.
- Any displayed synchronization, permission, or validation errors.
- Whether the issue affects one Iteration or multiple Iterations.
# Preventive guidance
- Close sprints through Jira so the Jira sprint remains the source of truth.
- Do not manually change statuses for Iterations managed by automatic sprint-based timeboxes.
- Periodically review historical Iterations after sprint closure, especially before preparing roadmap or leadership reports.
- Keep the connected Jira board and integration permissions current.
- Use a manual resynchronization when a closed Jira sprint is not reflected promptly in BigPicture.
# Frequently asked questions
Should an Iteration close automatically when its end date passes?
Why is the manual Close action blocked?
Is there a separate configuration option for automatic closing?
What should support do if resynchronization does not fix the status?