---
title: "Resolving Workload Data Discrepancies in BigPicture and Jira Integration"
canonical: "https://support.appfire.com/space/SUPPORT/3613425754/Resolving%20Workload%20Data%20Discrepancies%20in%20BigPicture%20and%20Jira%20Integration"
format: markdown
---
The article covers three distinct use cases related to workload visibility and estimation warnings in BigPicture:

1. **Workload showing 0% or "Unestimated"** despite values existing in Jira (Original/Remaining Estimates).
2. **Story Points not appearing** in the Resource module flyout.
3. **"Distributed workload is not equal to Remaining estimate"** warning message.

---

## Use Case 1: Workload shows 0% or "Unestimated" despite Jira data

### Problem

Users may observe that the BigPicture Resource module shows 0% workload or marks tasks as "unestimated" even when the underlying Jira tickets have values in the **Original Estimate** or **Remaining Estimate** fields. This often occurs after manual manipulation of estimates or automation updates.

### Solution: Resync Tasks via Gantt Module

The data discrepancy between Jira and BigPicture's Resource module can typically be resolved by triggering a resync.

1. Navigate to the **Gantt module** for the affected project/box.
2. Perform a **Resync** of the tasks.
3. Return to the **Resource module** to verify that the workload bars and flyout boxes now reflect the correct Jira data.

---

## Use Case 2: Story Points not appearing in Resource Module

### Problem

When using "Story Points" mode in the Resource module, the flyout boxes may show "No Story Points" even if the Jira ticket has a value in the standard `Story Points` field.

### Cause

BigPicture specifically looks for the **Estimated Story Points** field rather than the standard Jira `Story Points` field in certain configurations or UI views.

### Solution/Workaround

- **Verify Field Mapping:** Ensure that the field you are using in Jira is correctly mapped to the field BigPicture is reading (often "Estimated Story Points").
- **Check UI Labels:** Be aware that the UI label "Story Points" in the flyout may specifically refer to the "Estimated Story Points" value.

---

## Use Case 3: "Distributed workload is not equal to Remaining estimate" Warning

### Problem

In **Remaining Estimate mode**, a warning appears stating: *"Distributed workload is not equal to Remaining estimate. You can overwrite the Remaining estimate to make it equal."*

### Context

This warning appears when the manual distribution of hours across the timeline in BigPicture does not match the total value in the Jira `Remaining Estimate` field.

### Solution

- **To Align Data:** Clicking the **OVERWRITE** button will update the Jira Remaining Estimate to match the distributed workload in BigPicture.
- **To Maintain Discrepancy:** If you prefer to keep the discrepancy (e.g., to identify where estimates need improvement), you can ignore the warning. Note that the warning is informational regarding the lack of synchronization between the two values.