Home

›

Planner

›

Bookings

Planner feature

Resource Booking in Jira: Reserve Capacity by the Hour

Resource booking lets you staff a project before its Jira issues exist. A booking in ActivityTimeline reserves a set number of hours per day for a person or a whole team, and the workload indicator counts it right away, so nobody gets promised twice.

30-day free trial on the Atlassian Marketplace.

Sample ActivityTimeline Planner week in four steps. Emma Clark has free days, but the Atlas project has no Jira issues yet. A booking reserves 4 hours a day for Atlas, the day chips under her name show 10 hours on Monday and Tuesday because the booking overlaps her Jira work, and resizing the booking to start on Wednesday brings every day back within 8 hours.

Step 1

A new project, no Jira issues yet

Atlas starts this week and needs half of Emma Clark's time, but there is nothing in Jira to schedule.

Step 2

Create a booking

Click Emma's empty cell, choose Booking, pick the ATLAS project and set Hours per Day to 4.

Step 3

The workload indicator shows the clash

Monday and Tuesday turn red at 10 hours, because the booking overlaps her Jira work.

Step 4

Fix it on the timeline

Resize the booking to start on Wednesday. Every day is back within 8 hours, with 4 hours a day held for Atlas.

What Is Resource Booking in ActivityTimeline?

Resource booking in ActivityTimeline means placing a booking on a person's timeline. A booking is a planning item that reserves a person's capacity for a set number of hours per day, for a project or an activity, without scheduling a specific Jira issue. Bookings count in the workload indicator and in capacity forecasts, so managers see what is already promised and avoid overbooking.

You create bookings on the timeline of the ActivityTimeline Planner, next to people's Jira work and time off. An 8-hour booking on a day shows as 8 hours of planned work, even with no issue scheduled.

Part 1

Title and project

Name what the time is for. Pick a Jira project, or leave it under General for internal work.

Part 2

Hours per Day

The booking reserves the same hours on every working day. The pill on the bar shows the total for the period.

Part 3

Dates

Drag the booking to new dates or another person, or resize it to change its length.

Part 4

Approval

Administrators, Managers and Team Leads approve a booking to lock it.

Part 5

Workload indicator

The day chips under the name add booked hours to Jira work, so a clash turns the day red.

Sample ActivityTimeline Planner week for Emma Clark and Tom Becker. Emma has an approved booking, Atlas discovery, at 4 hours a day from Monday to Friday, 20 hours in total, next to the Jira issue PORT-112. The day chips under her name show 4, 4, 8, 8 and 4 hours.

Why use a booking and not a Jira issue?

The work isn't in Jira yet.

A signed project, a pilot or next quarter's roadmap has no backlog. A booking holds the people now, without placeholder tickets in your Jira projects.

You are planning time, not a task.

A Jira issue is a piece of work with an estimate and a done date. A booking is an allocation: 4 hours a day for Atlas, every working day of the period.

Some time never belongs in Jira.

Training, support rotations and interviews still use capacity. A booking under General shows them without a Jira project.

It stays in ActivityTimeline.

Bookings are stored in ActivityTimeline, not written to Jira. When the issues arrive, schedule them into the booked time and shorten or remove the booking.

When Do Teams Use Bookings?

Six moments when a resource manager or PMO needs to hold capacity that Jira can't show yet.

A deal is signed, the tickets come later

The statement of work starts in two weeks. Book the named people for the project now, then schedule issues into the time once the backlog exists.

A specialist is shared between projects

An architect gives 4 hours a day to one programme. Book those hours so other project leads see only the half that is left.

Support or on-call rotation

Each developer covers support one week a month. A recurring booking keeps that week out of sprint planning.

Training, onboarding and interviews

Internal work with no Jira issue still uses capacity. Book it under General, or with a custom type such as Training.

Whole-team events

Quarterly planning, a hackathon or a release week. One booking with Create for everyone in this team blocks the same days for every member.

Protecting an agreed allocation

The steering group agreed that two engineers are on the migration until March. Approve their bookings so nobody quietly reassigns the time.

What Can You Do with Bookings?

Reserve time for a person, a team or a recurring duty, see the effect on workload straight away, and lock the plan once it's agreed.

Reserve part of a day, not the whole person

Set Hours per Day to the share you need: 4 hours a day is half of a full-time specialist. The day chips under the name show at once whether the person still has room or is overbooked.

Sample Planner row: a 4-hours-a-day booking and the day chips under the name updating as Hours per Day changes.

Book a whole team in one step

Tick Create for everyone in this team, and the booking lands on every member's timeline for the same period.

Sample Create New Item dialog with Create for everyone in this team selected, and the booking added to each team member's timeline.

Approve to lock the plan

Once a booking is approved, Employees and other lower-level roles can't change it until an authorized user unapproves it.

Sample approved booking with the approval icon; an Employee's attempt to move it is blocked.

Make your own booking types

Administrators can add event types based on Booking, such as Training, Support or Interviews, each with its own name and worklog category. Mark a type as Not a Worklog when it should plan time but never count as time spent.

Repeat it with Recurrence

Block a weekly support rotation or a standing review with one recurring booking, up to 100 events per series.

Move, resize, split and clone

Drag a booking to another date or person, resize it, split a booking of two days or more, or clone it by dragging with Ctrl or Command held.

Count it in every forecast

Bookings feed the Resource Utilization Forecast and the Team Capacity Chart, next to Jira issues and placeholders.

How Do You Book Capacity in Jira with ActivityTimeline?

Three steps on the Planner. Try them in the dialog below: change the hours, the dates or the team option, then press Create.

Step 1 · Click an empty cell

On the person's timeline, click the day the booking should start. The Create New Item dialog opens; choose Booking.

Step 2 · Set title, project and hours

Enter a title, pick a project or keep General, set Hours per Day and the dates. Add Recurrence, an External Link or a Description if you need them.

Step 3 · Create and check the workload

Press Create. The booking appears on the timeline, and the day chips under each name show the hours planned for every day.

Sample Create New Item dialog with Booking selected: Title, Project (General), Hours per Day 4, Start Date and End Date, Recurrence, External Link, Description, and Create for everyone in this team.

Tip: hold Ctrl (Cmd on a Mac) while you drag a booking to clone it to another day or person.

All booking steps in the Help Center

Good to know before you book

Bookings in the past count as worklogs by default.

Turn this off in Timesheets Configuration, or per booking type with the Not a Worklog category.

Recurrence has a limit.

A recurring booking can have up to 100 events per series.

Deleting is final.

A deleted booking can't be restored, so check before you delete one.

Split needs two days.

Split works only on bookings of two days or more.

Booking vs Placeholder: Which One Should You Use?

Both hold capacity before the work is in Jira. A booking is a daily allocation; a placeholder is a block of estimated work.

Booking

How time is set

Hours per Day, the same on every working day

Link to a Jira issue

No. It sits under a project or General

What approval does

Locks the booking for lower-level roles

Counts in workload and forecasts

Yes

Book a whole team at once

Yes, with Create for everyone in this team

Best for

Fixed allocations: 4 hours a day, half a specialist, a weekly support rotation

Placeholder

How time is set

One total estimate for the whole duration

Link to a Jira issue

Standalone, or linked to an existing Jira issue

What approval does

Replaces the placeholder with the Jira issue

Counts in workload and forecasts

Yes

Book a whole team at once

One person per placeholder

Best for

Broader demand: a future phase, an unconfirmed project, extra QA effort

Source: ActivityTimeline Help Center, Booking Custom Event and Placeholder Custom Event, checked November 2026.

Bookings FAQ

Answers to what resource managers ask before they reserve capacity.

Still have a question?

Contact us through the support portal
What is resource booking in Jira?
Resource booking means reserving a person's time for a project before the work is assigned. Jira has no booking item of its own. In ActivityTimeline, a booking reserves a set number of hours per day on a person's timeline, without a Jira issue, and counts in their workload.
How is a booking different from a placeholder?
A booking sets Hours per Day, so it fits fixed allocations such as 4 hours a day. A placeholder uses one total estimate for its whole duration and can be linked to a Jira issue. Approving a placeholder replaces it with the Jira issue; approving a booking locks it.
Do bookings count toward workload and capacity reports?
Yes. Booked hours show in the workload indicator as planned work, even when no Jira issue is scheduled. They are also included in the Resource Utilization Forecast and the Team Capacity Chart, next to Jira issues and placeholders.
Do bookings show up in timesheets?
By default, yes: bookings in the past are treated as worklogs. If your timesheets should only hold Jira worklogs, clear Treat Booking items as worklogs in the Timesheets configuration, or set a booking type to the Not a Worklog category.
Can I book a whole team at once?
Yes. In the Create New Item dialog, select Create for everyone in this team. ActivityTimeline adds the booking to each team member's timeline for the selected period, which suits planning days, release weeks and team training.
Who can approve a booking?
Users with the required permissions, such as Administrators, Managers and Team Leads. An approved booking is locked: Employees and other lower-level roles can't change it. Click the approval icon again to unapprove it.
When should I use a booking instead of a Jira issue?
Use a booking when you need to hold a person's time but the work is not in Jira yet, or never will be: a signed project with no backlog, a share of a specialist, a support rotation, training. Bookings stay in ActivityTimeline and add no tickets to Jira. Once the issues exist, schedule them into the booked time.
Can bookings be created through the REST API?
Yes. Bookings, like other custom events, can be created and updated through the ActivityTimeline REST API, including the hours per day, the project and the approval state.

Reserve Next Quarter's Capacity Today

Book your own teams on your own Jira projects for 30 days, or let us walk your PMO through bookings in a 25-minute demo.

30-day free trial on the Atlassian Marketplace.