Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
  • Community
  • Q&A
  • Jira
  • Questions
  • Can we request that Workload Pie Chart gadget should support ΣOriginal Estimate / Σ Remaining Estima

Can we request that Workload Pie Chart gadget should support ΣOriginal Estimate / Σ Remaining Estima

Ed Maschler
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 30, 2026

"Workload Pie Chart gadget should support Σ Original Estimate / Σ Remaining Estimate / Σ Time Spent aggregate fields. Currently it only reads the flat Original Estimate field on each issue, which means subtask estimates are completely ignored. This makes the gadget useless for teams that estimate at the subtask level."

4 answers

0 votes
Marlene Kegel - codefortynine
Atlassian Partner
May 4, 2026

Welcome to the community, @Ed Maschler.

I am Marlene, working on the team who develops Quick Filters for Jira Dashboards.

You could also check out our app, if it works for you, since we provide more flexibility which number fields to aggregate within the Quick Pie Chart gadget (as you can see in the configuration below). Besides "work item counts" it can aggregate any Jira number field. 

This is also possible with other gadgets, like "Quick Two Dimensional Filter Statistics", "Quick Time Series", or "Quick Bar Chart".

On top of that all gadgets can be dynamically filtered with a "Quick Controller".

Quick-Filters-Jira-Dashboards_pie-chart-configuration.png 

0 votes
Ivan Manolov - JXL
Contributor
May 4, 2026

Hi @Ed Maschler,

Welcome to the Community.

You're right that the native Workload Pie Chart only reads the flat Original Estimate on each issue in the filter, which is a real limitation when estimation lives at the subtask level.

A couple of native angles worth trying:

  • Include subtasks in the filter. As @Danut M _StonikByte_ suggested, write your saved filter so it returns the subtasks themselves (e.g., project = ABC AND issuetype in standardIssueTypes() OR (parent in (project = ABC) AND issuetype in subtaskIssueTypes())), then point the gadget at that filter. The pie will now slice by assignee using the subtask estimates directly. The downside is parents and subtasks both contribute, so de-duplicate by removing parents from the filter if you only want subtask hours.
  • Use the Σ aggregate fields where they exist natively. "Σ Original Estimate", "Σ Remaining Estimate", and "Σ Time Spent" do show up on the work item view and in JQL via the parent's rolled-up time tracking, but not as gadget configuration options. So they help in the issue navigator and on individual epics, not on the Pie Chart.

If the goal is purely an executive view rather than the Pie Chart specifically, the Two-Dimensional Filter Statistics gadget with Assignee × Status (or Assignee × Σ Original Estimate via a custom-field workaround) can give you a similar workload picture once subtasks are included in the filter.

Hope this helps,

Ivan

Ivan Manolov - JXL
Contributor
May 4, 2026

@Ed MaschlerOne more thing worth mentioning, in case the gadget keeps falling short for your use case.

If you're open to solutions from the Atlassian Marketplace, JXL is a spreadsheet-style view for Jira that handles this directly. With its hierarchy and sum-up features, you can list parents (epics, stories, or any other level) and have Σ Original Estimate, Σ Remaining Estimate, and Σ Time Spent automatically rolled up from their subtasks into the parent row, including across multiple hierarchy levels. You can group by Assignee to get the same workload-by-person view the Pie Chart was meant to give you, but with subtask estimates properly counted. Sheets can also be embedded as a dashboard gadget for your executive view.

epic-original-estimate-sum-up.gif

Disclosure: I work for the team that builds JXL.

Cheers,

Ivan

0 votes
Danut M _StonikByte_
Atlassian Partner
April 30, 2026

Hi @Ed Maschler,

Welcome to the Atlassian Community.

Indeed, the native Jira's Workload Pie Chart gadget does not support those fields. A quick solution would be to configure the gadget with a filter that returns also the sub-tasks.

Another solution would be to search for a plugin (app) on Atlassian Marketplace for a gadget that supports these fields.  

If you are open to trying a plugin, our Great Gadgets app offers two gadgets that can display this: Pivot Table & Pivot Chart gadget and Worklog Reports & Timesheets gadget.

image.png

To display such chart, the gadget should be configured like this:

image.png

 

Hope this helps.

Danut.

0 votes
Eduardo Anflor - MindPro
Atlassian Partner
April 30, 2026

Hi, @Ed Maschler 

Welcome to the community! I am not sure you can meet exactly these requirements with Jira's out-of-the-box functionalities. If you are open to a marketplace solution, I recommend Mindpro Insights. I work at Mindpro, and I believe the app can help with this scenario.

It allows anyone to create and share dashboards with dynamic gadgets easily. It means when you click on a chart segment, the entire dashboard adapts to the filter. You can choose from over 50+ available.

For example, you can create a custom table chart that shows the estimates per user or use a pre-loaded chart that shows this information (you can define how the custom chart aggregates data), or add other custom charts to complement the vision:

 

Screenshot 2026-04-30 at 17.09.17.png

I hope that helps.

 

Regards,

Eduardo

 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin Site Admin
TAGS
AUG Leaders

Atlassian Community Events