QuickSight Bar Chart Double-Counting Planned Hours Per Issue

Q&A
,
1

Sample Dataset

project_name project_key issue_key start_week end_week author planned_hours
DCH-0087758 - URL 58_IAG1_LH URL58 URL58-40 2025-10-27 2025-11-02 user 1 10
DCH-0087758 - URL 58_IAG1_LH URL58 URL58-40 2025-09-01 2025-09-07 user2 10
DCH-0087758 - URL 58_IAG1_LH URL58 URL58-40 2025-09-01 2025-09-07 user1 10
DCH-0087758 - URL 58_IAG1_LH URL58 URL58-40 2025-09-15 2025-09-21 user3 10
DCH-0087758 - URL 58_IAG1_LH URL58 URL58-40 2025-09-22 2025-09-28 user4 10
DCH-0087758 - URL 58_IAG1_LH URL58 URL58-40 2025-10-06 2025-10-12 user4 10

On my dashboard, I have global filters for project_key, author, and week duration.

I have a bar chart that is supposed to show planned hours per project based on the selected filters.

For example, if I set the week filter from 2025-10-06 through 2025-11-02, QuickSight returns these two rows:

project_name project_key issue_key start_week end_week author planned_hours
DCH-0087758 - URL 58_IAG1_LH URL58 URL58-40 2025-10-27 2025-11-02 user1 10
DCH-0087758 - URL 58_IAG1_LH URL58 URL58-40 2025-10-06 2025-10-12 user4 10

Since it is the same project and same issue, I expect the bar chart to show 10 hours, not 20.

The issue is that planned_hours is the same across rows for the same issue_key, so QuickSight sums both rows. I tried using a calculated field with maxOver, but it still shows 20 instead of 10.

Has anyone encountered this problem or have suggestions on how to prevent double-counting planned hours per issue in a QuickSight bar chart when filters are applied?

2

Hi @sree,

What’s the calculation(s) you’re using in your bar chart? Could you share a screenshot of how you have it setup and what fields you’re using for each axis?
Could you also share the maxOver calculation that you built so that we can see why it was producing 20 instead of 10?

3

I tried different things.

example dataset -

Column 1 Column 2 Column 3 Column 4 E F G H I J
project_name project_key issue_key start_week end_week actual_hours author planned_hours_week_level remaining_hours_issue_level My comments
DCH-0087758 - URL 58_IAG1_LH URL58 URL58-31 2025-10-13 2025-10-19 0.5 Seppe Vercauteren 20 0
DCH-0087758 - URL 58_IAG1_LH URL58 URL58-40 2025-10-27 2025-11-02 0.33 Jofry Van de Walle 10 0
DCH-0087758 - URL 58_IAG1_LH URL58 URL58-40 2025-10-06 2025-10-12 2 Herman Goossens 10 0 should be counted only once
DCH-0087758 - URL 58_IAG1_LH URL58 URL58-43 2025-10-06 2025-10-12 1 Kevin Brems 20 0
DCH-0087758 - URL 58_IAG1_LH URL58 URL58-44 2025-10-13 2025-10-19 0.17 Kevin Brems 20 19.833333333333332
DCH-0087758 - URL 58_IAG1_LH URL58 URL58-45 2025-10-27 2025-11-02 0.33 Jofry Van de Walle 10 0
DCH-0087758 - URL 58_IAG1_LH URL58 URL58-51 2025-10-06 2025-10-12 0.25 Kevin Brems 0 0
DCH-0087758 - URL 58_IAG1_LH URL58 URL58-53 2025-10-06 2025-10-12 0.25 Kevin Brems 0 0
DCH-0087758 - URL 58_IAG1_LH URL58 URL58-63 2025-10-06 2025-10-12 0.17 Rita Raman 0.5 0
DCH-0087758 - URL 58_IAG1_LH URL58 URL58-64 2025-10-06 2025-10-12 0.17 Rita Raman 0.5 0
91 �

Quicksight Calculation -

Total Planned Hours = maxOver({planned_hours_week_level}, [{issue_key}], PRE_AGG)

Stacked Bar Combo Chart -
X-Axis = Project Key
Bars = Quicksight calculation - SUM(Total Planned Hours).
shows as 91 whereas it should be 81.

4

I figured out the calculated field and now i am getting the right result.

calculated field -
Total Planned Hours = sum(

max({planned_hours_week_level}, [{issue_key}])

)

1 Like