Auto Light Dark
Auto Light Dark
Breadcrumbs

Edit a Booking Flow

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



Requirements

  • You must by a Jira Administrator or be granted the permission to edit Booking Flows. For more details, refer to the Permissions article.



Edit a Booking Flow

  1. In the Booking Hub, click the Open button next to the Booking Flow you want to edit.

  2. Click Editing Booking Flow.

  3. Define the settings for each of the following tabs:


General Tab

Configure the following settings in the General tab:

  • 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.

  • Space: Select the Jira space used for booking requests.

  • Work Type: Choose the work item type used for booking requests.

Custom Fields

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.


Resources Tab

Define how the resource pool is managed for this Booking Flow. You have two options:

Important

Switching between resource management options (Booking ⇄ Assets) in an existing flow is not recommended, as it may break your booking history. If you need to switch, we suggest creating a new Booking Flow instead.

Option 1: Define and manage your resources in Apwide Booking

  • Click Edit list to update the list of resources.

Option 2: Define and manage your resources using Jira Assets (AQL)

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

Note

This option is only available when Jira Assets is enabled on the Jira instance.

  • AQL query: the system generates a default AQL query based on your schema and object type. You can customize this query to apply filters when needed. Use the Test button to verify that the query returns the expected resources.

  • (optional) Choose ‘Select’ or ‘Object’ attributes to be displayed as resource filters.

  • (optional) Choose an ‘Integer’ attribute to be used as capacity. This option is part of the advanced edition and not available in the Time Slots booking experience.

Common fields

  • Resource type: type of resource being booked (for example: Desk, Doctor, Projector, etc.)

  • advanced edition Additional resources: select already existing booking flows, so that additional resources are booked alongside the main one, for the same time range.


Workflow Tab

  • Confirmed Statuses: Define the statuses that represent valid bookings. Only bookings with these statuses will be included in the conflict-checking process.

Toggle to enable or disable the automated linking of conflicting booking requests. Conflict are checked whenever the Start field, End field, Booking field, or Status of a work item is updated, regardless of its status. Only work items in confirmed statuses are taken into consideration for detecting conflicts.

  • Link Type: If Link Conflict is enabled, select the issue link type to use for linking conflicting booking requests.

Auto-Approval

Toggle to enable or disable the auto-approval of booking requests.

  • Trigger Status: triggers the auto-approval when the work item reaches this status.

  • Approved: Set the target status for approved tickets.

  • Rejected: Set the target status for rejected tickets.

image-20250414-165631.png
Workflow example


Availability Tab

For details on configuring the Availability tab, refer to the Customize the Booking Experience documentation.


Permissions Tab

advanced edition

Jira Administrators can delegate the configuration of a Booking Flow to specific users or groups.

This allows non-admin users to manage Booking Flow settings without requiring full Jira admin rights.

For more information, refer to the Permissions documentation.