---
title: "How Jira Teams assignments affect capacity utilization in BigPicture."
canonical: "https://support.appfire.com/space/SUPPORT/3712876610/How%20Jira%20Teams%20assignments%20affect%20capacity%20utilization%20in%20BigPicture."
format: markdown
---
This article explains how to reflect Jira Team assignments in BigPicture Cloud and clarifies how this workaround affects resource reporting. Due to current Atlassian Forge API limitations, native integration between Jira Teams and BigPicture Teams is not available. This article covers two primary use cases:

1. Synchronizing team assignments for visual grouping in the Resources module.
2. Understanding the impact on capacity, utilization, and workload reporting.

## Problem

Users who have configured Atlassian Official Teams in Jira find that these assignments do not automatically flow into BigPicture. Consequently, the **Resources** tab may not show tasks under the correct team swimlanes, and workload data may appear empty or misaligned at the team level.

## Cause

Jira Teams do not natively integrate with BigPicture on the Forge platform because the necessary Atlassian APIs are currently unavailable. This is a known limitation tracked by Atlassian under [https://jira.atlassian.com/browse/JRACLOUD-92072](https://jira.atlassian.com/browse/JRACLOUD-92072) .

## Solution/Workaround

### Use Case 1: Synchronizing Jira Team Assignments to BigPicture

To ensure tasks appear in the correct team swimlanes within the BigPicture Resources module, you can map the **BigPicture Team Code** to a Jira field.

1. **Identify or Create a Jira Field:** Use a field such as **Labels** or a **Select List (single choice)** to represent your teams in Jira.
2. **Configure Team Codes in BigPicture:**
  - Navigate to the **Teams** module in BigPicture.
  - Ensure the **Team Code** for each BigPicture team matches the value used in your Jira field (e.g., if the Jira label is `Dev-Team-A`, the BigPicture Team Code must be `Dev-Team-A`).
3. **Map the Fields:**
  - Go to **App Configuration > Jira Software integration > Task configuration**.
  - Map the **Team Code** field to your chosen Jira field.
4. **(Optional) Automate the Sync:**
  - Use **Jira Automation** to automatically populate your mapped field whenever the "Atlassian Official Team" field is updated on an issue.

### Use Case 2: Understanding Reporting (Utilization vs. Allocation)

It is important to distinguish between **Team Assignment** (visual grouping) and **Workload/Capacity Calculation** (data reporting).

#### Capacity Calculation

Team capacity in BigPicture is **not** pulled from Jira. It is calculated based on:

- **Team Membership:** The sum of individual members' capacities.
- **Availability:** Each member's availability percentage defined within the BigPicture team.
- **Plans:** Workload plans, Holiday plans, and individual absences configured in BigPicture.

#### Workload and Utilization

The workaround ensures tasks are grouped correctly, but the actual hours/utilization are derived from:

- **Assignee:** The individual user assigned to the task.
- **Estimates:** Original Estimate, Remaining Estimate, or Story Points (based on your <u>[Effort Mode](https://support.appfire.com/space/DLP/2211743971/Effort+modes)</u>).
- **Contouring:** How effort is distributed over the task duration (Flat, Front-loaded, or Back-loaded).

| Feature | Source of Data | Affected by Workaround? |
| --- | --- | --- |
| **Team Swimlane** | Mapped Jira Field (Team Code) | **Yes** |
| **Individual Workload** | Task Estimates + Assignee | No |
| **Team Capacity** | BigPicture Team Membership + Plans | No |
| **Utilization %** | Workload vs. Capacity | **Yes** (via correct grouping) |