Change Logs

11.7 (2026-06-09)

Automatic Resource Selection

New Feature advanced We've introduced a new Automatic selection (random) mode in the Resources tab when editing a Booking Flow. When enabled, users can create bookings without selecting a resource, and Apwide Booking automatically selects a random available resource.

The resource field is hidden from the Time Selection and Time Slots booking experiences. The Resource Availability booking experience is not compatible with automatic selection, as users must first select a resource to view its availability.

This capability is also supported by the Create Apwide Booking automation action. If the Resource field is left empty, a random available resource is automatically selected.

Activity Tab Revamp

New Feature We've revamped the Booking Activity Tab available on all Jira work items part of a Booking Flow. The tab now provides more detailed booking information and allows users to manually trigger a conflict check.

This is especially useful for teams using manual approval workflows, as approvers can review potential conflicts before deciding whether to approve a booking.

bugfix Fixed an issue where creating a booking in the past from the timeline could open the booking screen without correctly identifying the selected date.

bugfix Fixed an issue in the Resource Availability booking experience where bookings with a limited availability range were displayed as extending until midnight.

bugfix Fixed an issue where the minimum notice time was not enforced when creating bookings from the timeline in the Time Slots booking experience.

bugfix Fixed an issue where incorrect start dates and durations could be displayed when rescheduling a booking from a workflow transition screen.

bugfix Fixed an issue where the booking flow creation was opening in a new tab.

11.5 & 11.6 (2026-05-21)

Resource Capacity

New Feature advanced We've introduced Resource Capacity, allowing resources stored in Assets to support multiple parallel bookings up to a defined capacity. Each booking consumes part of the available capacity, helping teams manage shared resources more accurately.

For example, a resource can represent percentages, units, seats, or parallel sessions. A booking may consume only part of the total capacity, while the remaining availability stays bookable for the same time range.

To support this new feature, we've added a quantity selector to the Booking field when capacity is enabled, improved the Booking custom field display, and added maximum capacity visibility directly in the timeline.

Learn more: Edit a Booking Flow documentation

improvement In the Edit Booking Flow screen, the Approval tab has been renamed to Workflow, with improved clarity around the Link conflicts and Auto-approval configuration.

improvement Conflict detection is now checked whenever the Start field, End field, Booking field, or Status of a work item is updated, regardless of its status. Previously, conflicts were only checked when a work item reached the trigger status.

Conflicting booking requests are now linked only if both requests are in a confirmed status. Previously, rejected requests could still remain linked to approved requests. To understand why a request was rejected, check the Booking activity panel.

improvement Removed reschedule operations from the user interface when auto-approval is disabled, as the target status cannot be determined. For custom workflows without auto-approval, we recommend using a workflow transition with a transition screen displaying the Booking field to let users reschedule bookings.

improvement We’ve improved the filter experience in both the Booking field and the List tab of the Booking Hub. Filters are now grouped under the funnel icon for a cleaner and more consistent interface.

bugfix Fixed an issue where the Booking Hub did not use the full available width in some browsers.

bugfix Fixed an issue where the end time could be incorrect when rescheduling bookings from the timeline if the user's time zone differed from the Jira instance time zone.

11.4 (2026-05-04)

improvement Create booking requests without a resource selected — Booking requests can now be submitted without specifying a resource upfront, allowing agents to assign one later in the workflow.

improvement Support for Jira's migration from field configurations to field schemes — Apwide Booking is now compatible with Jira's upcoming transition away from field configuration schemes. See this Atlassian Community article for details on how this change will affect all Jira users.

bugfix Fixed an issue where the Assets filters drop-down was not fully displayed in the Booking field.

11.3 (2026-04-23)

improvement Improved conflict visualization in both Resource Availability and Time Selection booking experiences.

improvement Improved date range visualization in the Resource Availability calendar.

improvement “Book” buttons are now hidden for users who do not have permission to create work items in the selected Booking Flow.

bugfix Minor UX improvements and fixes.

11.2 (2026-04-15)

Booking Flow Permissions

New Feature advanced Added a Permissions tab that allows Jira Administrators to delegate the configuration of Booking Flows to specific users or groups. Booking Flow creation remains restricted to Jira Administrators, as it involves Jira configuration.

Learn more: Permissions documentation

improvement Improved the Timeline tab UX to make browsing, scheduling, and rescheduling more intuitive directly from the timeline view.

improvement Replaced auto-save in Booking Flow configuration with explicit Save and Cancel actions, for better clarity and predictability.

bugfix Fixed an issue where the Refresh button did not animate after being clicked.

bugfix Fixed an issue where the duration label was not always visible in the anonymous JSM portal.

bugfix Fixed an issue where parking slot template data resulted in no available slots because slot durations exceeded availability windows.

bugfix Fixed an issue where the Customer Portal link was only visible to Jira Administrators.

11.1 (2026-04-10)

Flexible Time Slot Durations

New Feature advanced With the Time Slots booking experience, you can define multiple time slot durations (e.g. 15m, 30m, 45m), allowing users to choose the duration that fits their needs.

Learn more: Booking experience documentation

improvement Time is now displayed according to the user’s Jira time format (12h or 24h), ensuring consistency with their profile settings.

improvement Improved the workflow created for new booking flows to include resolutions and align with standard Jira reporting. This change does not apply to existing workflows, but resolutions can be added manually.

improvement Improved links to the Jira Service Management portal. A new Customer Portal link now opens the first corresponding request directly in the portal. Links to all related request type configurations are also available in Edit Booking Flow, under the Customer Request Types section.

improvement In the Resource Availability booking experience, work item keys and summaries are no longer displayed on the anonymous JSM portal. They are replaced with a “Busy” placeholder, ensuring sensitive information is not exposed to anonymous users.

improvement When selecting a time slot, the resource picker now shows only available resources. Previously, all resources were listed and the time slot was disabled after selecting an unavailable resource.

bugfix Fixed an issue where dates before the Default Start Time could not be selected on the availability calendar.

bugfix Fixed an issue where Assets filters were not always displayed on the JSM anonymous portal.

bugfix Fixed an issue where the “Leave anyway” button did not work on some discard screens.

11.0 (2026-03-20)

Resource Availability Booking Experience

New Feature Standard A new booking experience is now available. Users can select a resource and a date to view its availability. Our booking flow templates have been improved to leverage this new experience.

Learn more: Booking Experience documentation

Rovo Skills for Atlassian Studio

New Feature Standard Three Rovo Skills are now available for reuse in custom Rovo Agents.

These skills allow you to:

• Customize agent behavior (language, tone, interaction style)

• Adapt booking flows to specific use cases

• Use booking capabilities in environments where the Apwide Rovo Agent is not supported

Learn more: Rovo Skills documentation

Jira Automation Action: Create Apwide Booking

New Feature Standard A new Jira Automation action is available to create bookings automatically.

You can:

• Trigger booking creation based on Jira events (for example, issue transitions)

• Create one or multiple bookings

• Link bookings to Jira work items

Learn more: Create Apwide Booking documentation

improvement The Jira booking screens have been updated so that the Start time and End time fields are no longer required. New Booking Flows no longer include these fields in the Creation and Reschedule screens. For existing screens that still contain these fields, a banner is displayed to help administrators identify and remove unnecessary fields.

improvement Improved the overall performance and responsiveness of the Booking Hub by migrating from uikit to custom UI.

improvement Revamped the missing permissions banners to provide additional information.

bugfix Fixed an issue where the Enter key did not add the next resource.

bugfix Fixed rendering issues with banners in dark mode.

bugfix Fixed an issue preventing booking flow creation when resource names contained leading or trailing spaces.

10.2 (2026-03-02)

bugfix Resolved an issue that broke the creation of the workflow if the resource name ended with a space character when using the Flow creation wizard.

10.1 (2026-02-26)

bugfix Resolved an issue where the time slot availability window appeared as undefined after completing the booking flow creation wizard.

bugfix Corrected the display of the inactive license banner in the Booking Hub.

bugfix Fixed the resource selection behavior to ensure the selected resource updates properly after clicking a suggested resource.

10.0 (2026-02-26)

Assets Filtering

New Feature Standard We’ve introduced a new option that allows you to filter resources using ‘Select’ attributes defined on resources stored in Jira Assets.

9.14 (2026-03-02)

bugfix Resolved an issue that broke the creation of the workflow if the resource name ended with a space character when using the Flow creation wizard.

9.13 (2026-02-11)

improvement When creating a Custom Flow, we now only show the statuses filtered by selected Space and Work type.

9.12 (2026-02-11)

improvement Enhanced the error messages in custom Booking Flow creation.

9.11 (2026-02-05)

bugfix The Booking Flow wizard now allows using spaces in the name when creating a new Space for booking.

bugfix Resolved an issue that caused the JSM request type description to display “false” when no description was provided.

9.10 (2026-01-29)

Booking Flow Creation Wizard

New feature Standard Improved the Booking Flow creation process by introducing a multi-step wizard that guides users through the setup with clear steps:

• What to book: Define what users will book, replacing the previous template-based selection.

• Resource type: Choose the type of resources to book, such as in-app resources or Jira assets.

• Resource list: Select the specific resources available for booking.

• Jira space: Choose an existing Jira space or create a new one for the Booking Flow.

• Experience: Configure the Booking Experience and user-facing behavior.

• Summary: Review an overview of the selected configuration and start the Booking Flow creation.

• Completed: Confirm the successful creation of the Booking Flow, with options to open it or configure it further using the editing screen.

This guided approach improves clarity, reduces setup errors, and provides a smoother, more confident experience for Jira administrators. For detailed instructions, refer to the Create a Booking Flow documentation.

9.9 (2026-01-23)

bugfix Ensured headers are set correctly for all interactions with Jira to reduce the risk of incorrect default values.

9.8 (2026-01-20)

bugfix Fixed an issue where slot availability was miscalculated. In some cases, slots were incorrectly shown as available.

9.7 (2026-01-15)

improvement Added additional logging to help diagnose an issue that affects some users when creating new booking flows.

9.6 (2026-01-12)

Maximum Duration

New feature Standard Added an optional Maximum Duration setting to the Booking Flow configuration. This setting limits how long a resource can be booked when the user is able to change the duration. The limit applies to all bookings, including those created through the Rovo Agent.

improvement Improved the Rovo Agent performance by consolidating multiple skills.

improvement Updated the Booking logo to improve visibility in dark mode.

removal Deprecated the legacy resource storage method that stored resources as options in a select custom field. Resources must now be managed in Jira Assets or directly in the Booking App.