Resource management with ActivityTimeline Planner and Reports

Resource Management for Jira Teams in ActivityTimeline

Find people with the right skills, role and free time across all your Jira projects. Reserve their time, then assign the work in Jira without overloading anyone.

Skills with levels and a position on every person, set in bulk or from Jira groups

Free time by skill, level and position, week by week

Shared specialists, future hires and contractors in one plan

30-day free trial on the Atlassian Marketplace.

A staffing request in three steps. The Payments revamp project needs a senior React developer for 48 hours over three weeks from 30 November. The Skill / Level Availability Report shows two senior React developers: Ana Duarte has 8 hours free in those weeks and Leo Martins has 54; Emma Clark has time but at Middle level. A placeholder then reserves 48 hours on Leo's timeline, taking his weeks to 90, 95 and 100 percent without changing Jira. Approving it assigns the Jira issue PAY-112 to Leo.

One staffing request, three steps: find who has the skill and the free time, reserve it, then assign the work in Jira. Sample data: three delivery teams, 30 November to 18 December 2026.

What Resource Management Means in ActivityTimeline

Matching every request for people with someone who has the skill, the role and the free time, across all your Jira projects.

Eight people from three delivery teams, each with a position and skills with levels. Payments revamp needs a senior React developer for 48 hours: Leo Martins from the Mobile team has 54 hours free and takes it. Mobile release 5.2 needs a QA engineer for 24 hours in one week: no single QA engineer has that much, so Sam Carter takes 16 hours and Marco Rossi 8. Cloud migration needs a solution architect for 60 hours: Lena Fischer is the only one and has 44 hours free, so the plan is 16 hours short and needs a contractor or a later start.

Who can do it?

Skills, levels and positions

Skill chips such as React at Senior level and Java at Middle level, and positions such as QA engineer and Solution architect.

On every person in Planner

Who has the time?

Free hours across all projects

Free hours per week: Leo Martins 20 hours, Ana Duarte 2 hours, Sam Carter 16 hours.

Skill and Position Availability

What if nobody does?

Future hires and contractors

A future QA engineer added as a resource, with a placeholder reserving their time from 1 February.

Resources with placeholders

Popular capabilities

What You Can Do with Resource Management in ActivityTimeline

Everything a resource manager needs to answer "who can take this?", in one plan, from the people and work you already have in Jira.

Skills and proficiency levels

Give each person skills with a level, such as Senior Java or Middle React, so you can find the expertise you need in seconds.

In Planner →

Positions

Record each person's position, such as QA engineer or solution architect, and plan work by role, not only by name.

In Planner →

Skill and level availability

See who has a skill at the level you need, and how much of their time is still free, week by week.

In Reports →

Position availability

Check whether the people in a role have time for new work before you promise a start date.

In Reports →

Functional teams

Group people automatically by skill or position, such as all QA engineers across your delivery teams.

In Planner →

Shared specialists

See every commitment of a person shared between projects and teams on one timeline, so nobody gets booked twice.

In Planner →

Placeholders

Reserve a person's time for tentative work without touching Jira, then approve it into a Jira assignment.

In Planner →

Future hires and contractors

Plan open positions, new hires and contractors as resources with skills and capacity, before they have a Jira account.

In Planner →

Project Resources Forecast

See who is allocated to each project and for how many hours, week by week.

In Reports →

Split a task between people

Divide one Jira issue between several people, each with their own dates and hours.

In Planner →

Time off and availability

Take vacations, public holidays and work schedules off everyone's available time automatically.

In Workspace →

Bulk setup from Jira groups

Assign skills, positions and roles to many people at once, or map them from your Jira groups.

In Planner →

How to Manage Resources in ActivityTimeline

Set your people up once, then answer every staffing request from the same data: skills, positions and the work already planned in Jira.

1

Give every person skills, levels and a position

Add skills with a level, such as Senior React, and a position, such as QA engineer, to each person. Do it for many people at once, or map it from Jira groups so newcomers get it when they join. Then build functional teams on a skill or a position, such as everyone who knows Java, whatever their job title or team: they fill and update themselves.

A functional team built on the skill React: Ana Duarte and Leo Martins at Senior level and Emma Clark at Middle level, from the Web and Mobile teams. A team built on the skill Java brings together Emma Clark, Tom Becker and Lena Fischer, three people with three different job titles. When Nina Weber joins the frontend Jira group, she gets the Frontend engineer position and the React skill, and appears in the React team without anyone editing it.

2

Find who has the skill or role and the free time

When a project asks for people, start from the need, not from a team. The Skill / Level Availability Report and Position Availability list everyone who has the skill or position, grouped by level, with the hours they still have free each week after their work from every Jira project and their time off. Green means enough free time, yellow means it's limited.

Position Availability for QA engineers, 23 November to 18 December 2026: Maya Ortiz has 8, 10, 4 and 16 hours free in the four weeks, Marco Rossi 16, 16, 12 and 20 on a four-day week, and Sam Carter 20, 16, 16 and 20.

3

Share specialists across projects without double-booking them

Designers, QA engineers and architects often serve several projects at once. Their timeline shows all of it, so when two project managers book the same week, the overload is visible before anyone commits. Reassign the work to someone with the same position, move it, or split the issue between several people. The Project Resources Forecast then shows who carries each project.

Planner for the functional team QA engineers, four weeks from 23 November 2026. The Mobile team scheduled APP-140, 16 hours of regression testing, on Maya Ortiz in the week of 7 December, where she already has 36 hours of website release testing: 52 hours on 40, or 130%. Reassigning it to Sam Carter puts him at 100% and Maya at 90%. Splitting it gives Marco Rossi 8 hours (87.5%) and Sam 8 hours (80%).

4

Forecast roles for next quarter and plan new hires

Put next quarter's tentative projects on the plan as placeholders, then look at a functional team, such as all QA engineers, month by month. If a role runs short, add the future hire or contractor as a resource with a position, skills and capacity, and see whether the gap closes before you open the job.

Team Capacity Chart for the functional team QA engineers, January to March 2027, by month. Available capacity is 448, 448 and 520 hours. Confirmed Jira work is 380, 420 and 400 hours; with tentative projects as placeholders it is 410, 520 and 560, so February is at 116.07% and March at 107.69%. A future QA engineer added as a resource from 1 February adds 160 and 184 hours, bringing February to 85.53% and March to 79.55%.

Try it on your own people

Install ActivityTimeline from the Atlassian Marketplace and find who is free for your next request in an afternoon. Or let a product specialist walk you through it.

Common Resource Management Challenges, and How ActivityTimeline Handles Them

Resource management usually stalls for the same few reasons, in companies of every size. Here is where each one is handled.

Skills live in a spreadsheet nobody updates

Skills, levels and positions sit on each person, set in bulk or mapped from Jira groups. Functional teams built on them update themselves.

Every project manager books the same people

Each person has one timeline with work from every Jira project, so a second booking shows as overload before anyone commits to it.

Tentative plans turn into real assignments in Jira

Placeholders hold time on a person's timeline without changing Jira. Approve one, and only then does the issue get its assignee.

New hires and contractors aren't in Jira yet

Add them as resources with a position, skills and capacity, and reserve their time with placeholders until their account exists.

Nobody knows who is really available

Work schedules, public holidays and approved vacations come off everyone's available time, so free hours are real hours.

The plan lives in a tool people don't open

It runs inside Jira on the work your teams already have, and reports go on Jira dashboards and Confluence pages.

Have Questions About Resource Management in Your Company?

Bring one real staffing request. In 25 minutes a product specialist sets it up on sample people and shows how your resource managers would answer it in ActivityTimeline.

What the 25 minutes cover

0–8 min

Your staffing requests

Who asks for people, how often, and where it breaks today.

8–18 min

Skills, positions and availability

Set up on sample people, then find who is free for a real request.

18–25 min

Rollout across teams

Jira groups, functional teams, permissions and your questions.

Resource Management in ActivityTimeline: Questions

Short answers for resource managers and the people who roll ActivityTimeline out.

More answers in the Help Center
What is resource management in ActivityTimeline?
It is deciding who works on what across all your Jira projects, based on each person's skills, position and free time. ActivityTimeline keeps skills with levels and a position on every person, shows how much of their time is already planned across projects and teams, and lets you reserve time with placeholders before you assign the work in Jira.
How do I find people with a specific skill or role?
Give people skills with a proficiency level, such as Senior React, and a position, such as QA engineer. The Skill Availability, Skill / Level Availability and Position Availability reports then show who has the skill or position and how much of their time is still free, week by week. Functional teams also group people by skill or position automatically, so you can open all QA engineers in one Planner view.
Can several projects share the same specialist?
Yes. A person can belong to several teams, and their timeline always shows their work from every Jira project, plus bookings, placeholders and time off. If a second project asks for time they don't have, their workload indicator shows the overload before the work starts, and you can reassign the work, move it to a later week or split the issue between several people.
Can we plan for new hires and contractors who aren't in Jira yet?
Yes. Add them as resources with a position, skills, capacity and teams, and they appear in the plan and in capacity reports like everyone else. Jira issues can't be assigned to a resource directly, so reserve their time with placeholders, and reassign the work to their Jira account once they join.
Do we have to enter skills for every person by hand?
No. You can assign skills and positions to many people at once, or map them from Jira groups so people get them when they join a group. Functional teams built on those skills and positions then update themselves.
What is the difference between resource management and capacity planning?
Capacity planning asks how much work a person or team can take on in a period. Resource management asks who should do each piece of work: the person with the right skill, level and free time, across all projects. ActivityTimeline uses the same plan for both, so a staffing decision updates everyone's capacity straight away.
How do we try it?
Start a 30-day free trial from the Atlassian Marketplace on your own Jira projects. Or schedule a demo, and a product specialist finds the right people for one of your real staffing requests.

Find the Right People for Every Jira Project

Skills, positions and free time for everyone, in the Jira you already use. Built with Planner and Reports; time off comes from Workspace.

✓ 30-day free trial

✓ SOC 2 Type II and ISO 27001

✓ Runs inside Jira

The Planner with three functional teams, React developers, QA engineers and AWS engineers, and each person's workload for the next four weeks.