Editing a Booking Flow

In this article, you'll learn how to edit an already existing Booking Flow.

Info

The process described in this article also applies to creating a Custom Booking Flow.

Requirements

You must be a Jira Administrator to edit Booking Flows. For more details, refer to the Permissions article.

In the Booking Hub, click the Open button to open the Booking Flow you want to edit.
Click the Booking Flow grey button.
Click the Edit button and define the following settings:

Enabled: Enable or disable the Booking Flow using the toggle. Disabled flows are moved to the Disabled Configuration section in the Booking Hub.
Name: Enter a name for the Booking Flow.
Description: Provide a description.
Project: Select the Jira project used for booking requests.
Work Type: Choose the work item type used for booking requests.

Important

The following fields must be available on the Create screen for the selected issue type.

Start field: Select the Date-Time Picker custom field used for the start time of the booking.
End field: Select the Date-Time Picker custom field used for the end time of the booking.
Resource field: Select the Booking custom field used for the resource being booked.

You can define how the resource pool is managed for this Booking Flow.

Define and manage your resources in Apwide Booking: Add and manage resources inside the Booking App.
Define and manage your resources using Jira Assets (AQL): Connect to a Jira Assets schema and pull in objects using an AQL (Assets Query Language) filter. This option is only available when Jira Assets is available on the Jira instance.
- Resource Type: Give your resource type a clear, descriptive name—e.g., Desk, Parking Slot, or Projector. This is the label users will see when booking.
- Schema: Select the Jira Assets schema where your resources are stored.
- Object Type: Choose the object type within that schema (e.g., “Parking Slot”).
- AQL Query: The system generates a default AQL query based on your schema and object type. You can customize this query to apply filters—e.g., Color = "Green" to show only green parking slots.
- Test: Use the Test button to verify that the query returns the expected resources.

Any updates to Jira Assets (adding/removing objects) are automatically reflected in the Booking Flow—no manual sync required.

Important

Switching between resource management modes (Booking ⇄ Assets) in an existing flow is not recommended, as it may break configuration history.

If you need to switch, we suggest creating a new Booking Flow instead.

Link Conflicting Tickets: Toggle to enable or disable the automated linking of conflicting booking requests. When enabled, related conflicts are grouped together.
Issue Link Type: If Link Conflict is enabled, select the issue link type to use for linking conflicting booking requests.

Trigger Status: Choose the status that will trigger the conflict detection. When the Jira work item transitions to this status, conflicts will be checked, and an entry will be added to the Booking activity panel. If enabled, conflict linking and auto-approval will also be applied.
Confirmed Statuses: Define the statuses that represent valid bookings. Only bookings with these statuses will be included in the conflict-checking process.

Auto approve request: Toggle to enable or disable the auto-approval of booking requests. When enabled, a Jira work item that reaches the trigger status will be automatically transitioned to either the approved or rejected status.
- Approved: Set the target status for approved tickets.
- Rejected: Set the target status for rejected tickets.