---
title: "Understanding BigPicture Resources Module: Capacity and Team View Calculations"
canonical: "https://support.appfire.com/space/SUPPORT/3589934888/Understanding%20BigPicture%20Resources%20Module%3A%20Capacity%20and%20Team%20View%20Calculations"
format: markdown
---
Use this guide when customers ask how BigPicture Resources values are calculated, especially entries such as **0.8H / 40.0H**, team workload totals, and whether values apply to a specific box or the full Jira instance.

> ℹ️ **Best use case:** Documentation-style support questions from evaluators or customers who want clarification on the **Resources** module behavior in BigPicture Cloud.

# When to use this response pattern

- Customer asks what the first value in a resource capacity display means
- Customer wants to know whether logged time is calculated for the current Program/Project only or the whole Jira instance
- Customer asks how **Team view** totals are calculated
- Customer requests supporting documentation for the Resources module

# Core explanation to provide

> ✅ **Approved explanation:** In the Resources module, a value like **0.8H / 40.0H** means **0.8 hours logged** out of **40 available hours** for that resource during the selected time period.

- **First value:** actual work logged
- **Second value:** total available capacity for the selected period
- **Scope:** the logged time shown in this context applies to work items within the specific **Program/Project (box)** being viewed
- **Not instance-wide:** this is not the user’s total logged time across the entire Jira instance

# How to explain Team view

When the customer asks about Team view, explain that it shows the workload and total logged time for the **entire team** in the context of the currently viewed box.

- It aggregates values from team members
- It reflects work items assigned to those team members within the current box context
- It should not be described as a global Jira-wide team timesheet unless documentation explicitly says so for that scenario

> 📝 If the customer is comparing Team view with time tracking outside the box, remind them that the Resource module is context-sensitive and should be interpreted within the currently selected box and time period.

# Recommended support reply

> Hi [Customer Name],
> 
> Thank you for reaching out to BigPicture support.
> 
> In the Resources module, a value such as **0.8H / 40.0H** means that **0.8 hours have been logged** out of a total of **40 available hours** for that resource in the selected time period.
> 
> The logged value shown there reflects time recorded for work items within the specific **Program/Project (box)** you are currently viewing, rather than all work items across the whole Jira instance.
> 
> In **Team view**, the module displays workload and total logged time for the entire team by aggregating the hours of team members for work items assigned to them within that same box context.
> 
> For more details, please refer to the documentation here: [Capacity calculation](https://appfire.atlassian.net/wiki/spaces/DLP/pages/2212528792).
> 
> Please note that we do not have access to customer instance data, so we can clarify product behavior but cannot inspect box contents directly.
> 
> Best,  
> Appfire Support

# Suggested handling workflow

- [ ] Confirm the question is about BigPicture Resources module calculations
- [ ] Explain the meaning of the logged hours versus available hours format
- [ ] Clarify that the calculation is box-contextual, not instance-wide
- [ ] Explain Team view as aggregated team workload within the same box context
- [ ] Share the capacity calculation documentation link
- [ ] State clearly that Support cannot access the customer’s instance contents

# Do and don’t guidance

| Do | Don’t | Why it matters |
| --- | --- | --- |
| Explain the value as logged time out of available capacity | Describe it as a generic progress percentage | Customers are asking about time-based calculation, not status tracking |
| Anchor the answer to the selected box and time period | Suggest the figure includes all Jira work by default | This prevents incorrect expectations about instance-wide totals |
| Describe Team view as aggregated team data in current context | Call it a universal team timesheet without qualification | Team totals depend on scope and viewed context |
| Link the documentation article | Rely only on a short custom explanation | The doc gives the customer a durable self-service reference |

# Common pitfalls

> ⚠️ **Avoid overcommitting on data visibility.** If a customer shares a site link, do not imply Support can inspect their actual configuration or records unless access has been explicitly granted through an approved process.

- Do not say values are Jira-instance-wide unless verified for the exact view and setup
- Do not assume the customer understands that capacity depends on the selected period
- Do not skip the documentation link when the customer explicitly asks for detailed material

# Escalation guidance

Escalate or seek internal clarification if:

- The customer reports numbers that appear inconsistent with the documented box context
- The question involves unexpected calculation behavior rather than a usage explanation
- The issue may depend on configuration, app version differences, or a possible defect

<details>
<summary>Internal notes for support agents</summary>


</details>