Why is the Workload Pie Chart showing 0h for tasks with valid time logged?

[Teresa Shellvin]

Problem

Despite the fact that there are three unresolved HR tasks assigned to Hooria Fayyaz (under Arancia organization), the Workload Pie Chart widget is showing:

"No Data Available”

Total Time: 0

Current Estimate by Assignee: Empty

This is not correct, as the tasks have valid “Actual Hours” and “Spent Hours” logged (see screenshots attached). For example:

• Two of the tasks have:
    - Actual Hours: 3h
    - Spent Hours: 1h

• One task has:
    - Actual Hours: 1h
    - Spent Hours: 15m

What we expect

We expected the Workload Pie to show the capacity breakdown by assignee (Hooria), reflecting the Current Estimate time values. The widget should not be empty.

Our Configuration

• Filter used: HR Arancia Unresolved Tasks

• Statistic Type: Assignee

• Time field to report on: Current Estimate

• Refresh Interval: Every 15 minutes

• All tasks are unresolved and assigned to Hooria

Supporting evidence

• 3 tasks assigned to Hooria and unresolved

• Valid actual/spent hours on each

• Pie chart shows 0h total

• Config is set to show "Current Estimate by Assignee"

Request

Can you help us understand:

1. Why is the capacity pie chart showing 0h even though there are valid time estimates?

2. Is the “Current Estimate” field not pulling from actual hours or another field?

3. Do we need to change the Time field to report on to something else (e.g., Original Estimate or Remaining Estimate)?

4. Is there a known issue with this chart/filter interaction?

Please advise how we can resolve this or what we should adjust in configuration to get the correct chart output.

[Marc -Devoteam- · Accepted solution]

Hi @Teresa Shellvin 

The Workload Pie chard gadget work with the time tracking fields of Jira.

You can't use custom fields for this.

So it rather seems you are using custom fields or a 3rd party app from time tracking.

If an app is used which app, does that app provide it's own dashboard gadgets, is there anything in their documentaiton?

[Teresa Shellvin]

thanks , also i've to create a capacity-based workload dashboard for the IT / HR teams. The goal is to show actual workload by hours, not task count. This should include:

Requirements

1. Pull data from multiple IT / HR projects

2. Include only active items: To Do, In Progress, In Review, Blocked

3. Workload must show:

   • Total estimated hours

   • Remaining hours

   • Logged hours (optional)

   • Percentage of capacity used (40-hour week per person)

4. Dashboard widget should show workload by hours per assignee across all boards

5. Ideally a bar chart or table showing weekly totals

6. Issues with no estimates should be flagged

7. Dashboard should auto-refresh when filters update

Question

Is this fully achievable with standard Jira Cloud dashboards, or do I need an add-on for:

• Weekly capacity

• Capacity % used

• Combined view of estimate + remaining + logged hours

• Azure-DevOps-style weekly workload charts

If an add-on is required, which one is best for capacity planning ?

Any guidance, best practices, or examples would be appreciated.

Thank you!

[Rustem Shiriiazdanov _Actonic_ · Accepted solution]

Hi @Teresa Shellvin,

TLDR version of my text below: Considering that your fields names do not look standard, I assume you use some custom fields in your Jira setup to do the time tracking. So apparently, the gadget is not “reading” your Actual Hours / Spent Hours at all. It only looks at Jira’s built-in time tracking fields, and your selected field (“Current Estimate”) is effectively Remaining Estimate, which for those issues is probably 0 – so the pie shows 0h. I do not think it is a bug, it's apparently your Jira configuration which is not using standard Jira fields, and you either will have to switch to standard fields, or use some automation, or use non-standa4rd reporting apps to cope with that..

Re your questions one by one:

Why is the pie chart showing 0h with valid hours on the issues?

The Workload Pie Chart gadget works only with Jira’s native time tracking fields:

• Original Estimate

• Remaining Estimate (a.k.a. Estimated Time Remaining / Current Estimate)

• Time Spent 

Estimated Time Remaining is the current estimate of the remaining amount of time it would take to complete this issue.

So if:

• the issues have no Remaining Estimate set, or

• Remaining Estimate has been driven to 0 (for example by logging work and choosing “Set remaining estimate to 0”)

then Current Estimate = 0 even though you see something in the fields “Actual Hours” / “Spent Hours” (which are likely custom fields or from an HR/time app).

Result: gadget sees 3 issues, but Current Estimate is 0 for all of them → total 0h → “No Data Available / Total Time: 0”.

Is “Current Estimate” pulling from Actual Hours or another field?

Unfortunately, I assume, it is not pulling from your “Actual Hours” or “Spent Hours” fields.

For Jira Cloud time tracking:

• Original Estimate – how much time you thought it would take.

• Time Spent – how much work has been logged in worklogs.

• Remaining Estimate / Estimated Time Remaining – how much time you believe is left; Atlassian docs call this the current estimate. 

• Many tools and docs express Current Estimate as Time Spent + Remaining or as “the current time tracking position” built from those two fields. 

The Workload Pie gadget’s “Current Estimate” setting is wired to the “Remaining Estimate / current estimate” from Jira’s time tracking, not to any custom fields called “Actual hours”, “Spent hours”, etc. 

So if those HR fields are the only ones populated, the gadget will still see 0 when looking at Current Estimate.

Do we need to change the Time field to something else / if this is a bug:

I don't think it is a bug. Most likely you indeed need to change your fields, depending on what you actually want to visualize:

1. If you want capacity by remaining planned time
   Then you must ensure Remaining Estimate is correctly filled on the issues:

   • Set Original Estimate when creating/planning the tasks.

   • When logging work, make sure Remaining Estimate is updated (not always set to 0).

   • Then keep Time field to report on = Current Estimate.

2. If you want capacity by already logged hours (work done)

   • Choose Time field to report on = Time Spent (assuming you log work via standard Jira worklogs).

   • The pie will then slice by sum(Time Spent) per assignee.

3. If your “Actual/Spent Hours” are custom fields from an app/HR scheme

   • The native Workload Pie gadget cannot use custom numeric fields. It really only supports Time Spent / Original Estimate / Current (Remaining) Estimate. 

   • To use those HR fields, you’d need either:

     • An automation that copies HR fields into the native time-tracking fields (if that makes sense process-wise), or

     • A different reporting mechanism (another app, or custom dashboard app) that can aggregate your custom time fields directly.

Regards,

Rustem