Setting up a capacity portfolio

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.

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 🙂

Welcome over from Asana, the capacity model is one of the bigger adjustments in that move, so this is a good question to work through carefully.

The A-or-B you're weighing is real, and it helps to separate what each native option is actually for:

A Plan (Advanced Roadmaps, Premium) is the closest native equivalent to a capacity portfolio. You pull multiple projects/boards into one plan, assign teams, and set each team's capacity. then the plan shows planned work against that capacity across teams on a timeline. This is the right tool if your main need is forward planning and "can these teams realistically take this on."

The thing to watch, coming from Asana specifically: Jira capacity is calculated from estimates on issues (story points or time), so a Plan's capacity view is only as good as your estimation discipline. In Asana you may have leaned on assignee workload; in Jira, if issues aren't estimated, the capacity math quietly reads everyone as fully available. So step one is really deciding your estimation basis — that decision drives whether either native option gives you trustworthy numbers.

Where Plans tends to strain is the live side — it models capacity at planning time, but doesn't show how much of it the in-flight and unplanned work is actually eating once the sprint is moving.

That live gap is what we work on at Everview (disclosure: I'm on the team). It sits on top of Jira (Jira stays your source of record) and reads your actual issues to show capacity as a live signal across teams and projects: committed load vs. real availability, updating as work moves rather than as a plan-time estimate. Since you're mid-migration, one relevant detail: it reads from Jira and Asana both, so if some teams haven't fully moved over yet, the capacity picture doesn't go blind on the half that's still in Asana.

On the Atlassian Marketplace if it's useful to look at: Evevrview.ai
Either way, I'd start by settling the estimation basis and trying a Plan first; that's the foundation the rest sits on.