Setting up a capacity portfolio

[Maryse Dupuy]

Hi Atlassian Community!

I am migrating my team from Asana to Jira, and I am having trouble setting up a workload/capacity portfolio.

From what I gather, I can either:

Create a Plan which shows all work assigned to Teams, with the capacity in hours for each Team.

or

Add a Capacity view to my Space, use a filter for each individual, but then the individual capacity is stuck at 40 hours, and the Epics don't automatically have a time value, I would need to manually add the time from each task to their parent Epic.

But what I am really looking for is a portfolio which shows workload per person, as well as their capacity in billable hours (which vary from person to person)

See examples from Asana here:

[Marc -Devoteam-]

Hi @Maryse Dupuy 

You need to use the "Plans" feature.

The space time-line is for the board and space related items only.

For more informatio, see what-is-advanced-planning 

Note the Atlassian vision and working os based on team not on individuals.

[Sami Shaik]

Hi @Maryse Dupuy 

Welcome from Asana, and @Marc -Devoteam-  has pointed you at the right engine, so let me fill in the three specifics your question is really about.

First, the pain you can delete today: stop adding task time to Epics by hand. In a Plan, turn on the roll-up setting (view settings) and estimates aggregate up the hierarchy automatically, task hours roll to their Epic. That part of your Asana muscle memory has a direct Jira equivalent, it just lives in Plans rather than the space view.

Second, the honest boundary, so you do not spend weeks searching for a screen that does not exist: Jira's native capacity model is team-based per sprint or iteration, exactly as Marc says. You can group a Plan's timeline by assignee to see each person's load, and that is genuinely useful, but a per-person, person-specific capacity number (your 32h vs their 24h of billable time) is not a native concept, and the new Capacity view you found (which is brand new from this summer's release, still maturing) currently reflects that with its fixed default.

So for the per-person billable-hours portfolio itself, two practical routes:

1. The native approximation: one filter per person, a dashboard with time-tracking gadgets showing Σ estimated vs logged per assignee, compared against each person's billable target (which lives in your head or a Confluence table). Free, ten minutes, and honestly sufficient for a small team.
2. The real answer if billable capacity is a hard requirement: this is exactly what the timesheet and resource-planning category of Marketplace apps exists for, per-person capacity profiles, billable vs non-billable hours, utilization reports. If billing accuracy matters commercially, that category is where Asana-style per-person portfolios actually live in the Jira ecosystem.

One migration kindness from someone who has watched many Asana-to-Jira moves: resist rebuilding Asana's person-centric model inside Jira, the platform will fight you. Plans plus roll-ups for the portfolio, dashboards for the person view, and a timesheet app if billing is real, that combination stops hurting within a month 🙂