Bugs in Capacity Management in Portfolios (Advanced plan)

English Forum Ask the Community
1

Context

  • Asana Advanced plan

  • Feature: Capacity Management (Workload / Capacity)

  • Using French-language UI

  • Using a Portfolio that aggregates capacity/hours across multiple projects

Issue 1: Portfolio capacity only shows hours for projects where Capacity is enabled

When a project is added to a Portfolio, I only see its hours/effort reflected in the Portfolio capacity view if that project has Capacity enabled.

If Capacity is not enabled on a given project, the project appears in the Portfolio, but its hours do not appear in the Portfolio’s capacity roll-up.

Question: Is it expected behavior that every project inside a Portfolio must have Capacity enabled in order for its hours/effort to roll up and be visible at the Portfolio level? Or is this a bug?

Issue 2: Hours appear duplicated / totals don’t match tasks

In the overall capacity summary view (global view of hours), I’m seeing totals that don’t match what actually exists in the project, and some hours appear to be double-counted.

Example from the screenshot: the project “Vacances et fériés” shows 77 hours.

But in reality, inside that project there are two tasks:

  • One task with 7 hours

  • One task with 35 hours

That should total 42 hours, but Asana shows 77 hours, which strongly suggests the 35-hour task is being counted twice, even though it appears only once in the project.

Question: Are there known scenarios where Capacity Management can double-count task hours? If not, I believe this is a bug.

Issue 3: Monthly total capacity is higher than expected (161h vs 140h)

In the same summary, Asana shows a monthly total capacity of 161 hours for a person.

However, the schedule is 35h/week, and for a typical 4-week month I would expect 35 x 4 = 140 hours.

Question: Is it normal for Asana’s Capacity Management to compute monthly capacity using a different method than “weekly hours x 4”? For example:

  • Does it calculate based on the exact number of working days in the month?

  • Does it include partial weeks at the beginning/end of the month?

  • Can holidays/time off rules affect the baseline monthly capacity?

  • Could locale settings influence how capacity is calculated?

If 161h is expected, I’d love clarification on the formula. If not, I suspect a bug in the monthly capacity calculation.

What I’m looking for

  1. Confirmation whether “projects must have Capacity enabled to roll up into Portfolio capacity” is expected.

  2. Any known causes or fixes for double-counted hours in capacity rollups.

  3. The official explanation/formula for how Asana calculates monthly capacity (e.g., why 161h can happen with a 35h/week schedule).

Screen capture

screen1
screen11906Ă—1766 467 KB

Screen2
Screen21222Ă—762 65.4 KB

2

Bonjour Claude,

Je me permets de répondre en français car j’ai vu la langue de votre interface. Par expérience, on croit souvent que le calcul du Workload est défaillant, alors qu’en fait c’est lié à une incompréhension de son fonctionnement. C’est difficile à débuger par écrit. Voulez-vous qu’on en discute lors d’un appel (gratuit) ?

English version: offering to help in French on a video call since this is hard to debug in writing

3

Hi! We are experiencing the same Bug Issue #2 today… was there any resolution following your call? :slight_smile:

4

Yes I did talk with Bastien.

He was able to replicate as well the issue on his side.

Our discussion was mainly about issue #2.

I have open a ticket using the link within the interface and filled a form. Still waiting for a confirmation from Asana.

image
image3866Ă—554 188 KB

1 Like