--- language: "en" --- # Apwide Booking ## Apwide Booking Assets Scheduling for Jira Cloud [Get Started](https://booking.apwide.com/doc/get-started.md) ### Topics * #### [Get Started](https://booking.apwide.com/doc/get-started.md) * #### [Booking Hub](https://booking.apwide.com/doc/booking-hub.md) #### [Booking Flows](https://booking.apwide.com/doc/booking-flow.md) #### [Rovo Agent](https://booking.apwide.com/doc/rovo-agent.md) #### [Jira Automation](https://booking.apwide.com/doc/jira-automation.md) * #### [Permissions](https://booking.apwide.com/doc/permissions.md) * #### [Troubleshooting](https://booking.apwide.com/doc/troubleshooting.md) #### [Change Logs](https://booking.apwide.com/doc/change-logs.md) --- language: "en" --- # Action: Create Apwide Booking Use the **Create Apwide Booking** action in Jira Automation to create a new booking in a booking flow. This action helps you automate booking creation based on Jira events, such as a work item transition. You can use it to create one or multiple bookings and link them to a work item. *** ** * ** *** ## Requirements * Access to **Jira Automation** * Familiarity with Jira Automation concepts (triggers, actions, smart values) * An existing booking flow in the Booking App *** ** * ** *** ## Add the Create Apwide Booking Action 1. Create or edit an automation rule in **Jira Automation**. 2. Select a trigger for the rule (for example, **Work item transitioned**). 3. Select **Add component** or **Add to branch**. 4. Search for and select **Create Apwide Booking**. 5. Configure the fields: 1. **Booking Flow**: The booking flow to create a booking in. 2. **Summary**: The summary of the booking request. Smart values are supported. 3. **Booking start** : Start date and time of the booking in ISO format. Smart values are supported. Example: `{{now.plusBusinessDays(9)}}` or `{{issue.customerfield_XXXXX}}` 4. **Booking end** : End date and time of the booking in ISO format. Smart values are supported. Example: `{{now.plusBusinessDays(15)}}` or `{{issue.customerfield_XXXXX}}` 5. **Resource name**: The resource assigned to the booking. Must exist in the Booking Flow. 6. Save and enable the automation rule. **Result:** A booking is created automatically when the rule is triggered. ![image-20260319-113712.png](https://booking.apwide.com/__attachments/a_96d1b173a487ad49fdcaaeba296653c6fac03605b8e1b1c3a50272d294981345/image-20260319-113712.png?cb=4c4a1d28aeb3435803528a39b5c9b3a2) Example of Create Apwide Booking Jira Automation Action *** ** * ** *** ## Verify the Automation Execution To verify that the booking was created: 1. Open the automation rule audit log. 2. Review the execution details and actions performed. 3. Open the related work item. 4. Check the activity or linked bookings. *** ** * ** *** ## Example: Automatically Book Equipment A company manages conference room bookings. 1. A conference room is booked through a work item. 2. The work item transitions to the *Book Equipment* status. 3. A Jira Automation rule is triggered. 4. The rule creates bookings for each required equipment using the **Create Apwide Booking** action. 5. The equipment bookings use the same dates as the room booking. 6. The bookings are linked to the original work item. **Result:** All related bookings are visible from the same work item. Users can track their status and take action if needed. --- language: "en" --- # Action: Edit Apwide Booking Use the **Edit Apwide Booking** action Jira Automation to update existing booking information automatically. This action edits booking values such as the start date, end date, and assigned resource. You can use this action to keep bookings in sync with changes in related work items. For example, when a parent work item changes status, all linked bookings can be updated automatically *** ** * ** *** ## Requirements * Access to **Jira Automation**. * Familiarity with creating **automation rules** and using **smart values**. *** ** * ** *** ## Add the Edit Apwide Booking Action 1. Create or edit an automation rule in **Jira Automation**. 2. Select a trigger for the rule (for example, **Manually triggered**). 3. Select **Add component** or **Add to branch**. 4. Search for and select **Edit Apwide Booking**. 5. Configure the fields: * **Work item** : The issue whose booking field you want to update. Example: `{{issue.key}}` or `{{triggerIssue.key}}` * **Booking start** : New booking start date. Supports smart values. Example: `{{now.plusBusinessDays(9)}}` * **Booking end** : New booking end date. Supports smart values. Example: `{{now.plusBusinessDays(15)}}` * **Resource name**: The resource assigned to the booking. Must exist in the Booking Flow. ![image-20251119-120711.png](https://booking.apwide.com/__attachments/a_d5d22cfe14279b20934f2d6c31ea186381d223d14f87a069802b3b54d529d27f/image-20251119-120711.png?cb=3ab0df4dbb2a10c9a6f395fca1342a28) Example of Edit Apwide Booking Jira Automation Action **Important** If conflict detection or auto-approval is enabled in your Booking Flow, you may need to transition the work item after the booking is updated. Use a separate **Transition work item** action in the rule. This step is not handled by the **Edit Apwide Booking** action. *** ** * ** *** ## Tracking Changes After the rule runs, you can verify what happened by: * Reviewing the automation rule log. * Checking issue activity in the work item. *** ** * ** *** ## Use Case Example A company manages a fleet of shared vehicles. When a vehicle requires repair, all overlapping bookings must be canceled. A new booking is created for the repair period and linked to the repair work item to block the vehicle. A Jira Automation rule runs when the repair status changes. The rule: * Cancels affected bookings. * Notifies reporters so they can book another vehicle. * Updates or creates a blocking booking using the **Edit Apwide Booking** action. As a result, the vehicle cannot be booked during the repair period, and availability remains accurate without manual updates. --- language: "en" --- # Block a resource for the whole day When someone books a resource, you may want to block this resource for the whole day. ![image-20260603-085734.png](https://booking.apwide.com/__attachments/a_4af8f95a82f555f181f82a359fed6d3ad49f95dce97d9406d292dc220a78a41d/image-20260603-085734.png?cb=08bef14b6e287a9bf1eecf9ed4793dea) When booking a pet, Jira Automation automatically blocks it for the whole day *** ** * ** *** ## Requirements * Booking Flow configured. * Access to **Jira Automation**. * Familiarity with creating **automation rules** and using **smart values**. *** ** * ** *** ## Configuration Create a new **Jira Automation** **rule** with the following configuration: ![image-20260603-090042.png](https://booking.apwide.com/__attachments/a_3d3d78fc7104705ca34b5b437ea76ce896cecea6325bdd86fe3a7d83909f3a73/image-20260603-090042.png?cb=d996153f1dd9a95d70ab9d7dece765c6) Jira Automation Configuration ### Trigger: Field value changed The rule will be triggered when your booking request is approved. ![image-20260603-090129.png](https://booking.apwide.com/__attachments/a_59df6d42c700b04fd9005375c3021f5e66ab6d32d700241d9cf46244b82299ec/image-20260603-090129.png?cb=854eedfb6055cff34f574de1890c6291) You can add a condition to only trigger the rule for the project and work type used by your Booking Flow. ### Action: Create Apwide Booking Create a second booking request that blocks the same resource for the whole day. ![image-20260603-090247.png](https://booking.apwide.com/__attachments/a_0814e6456c8f1d358c50d063a8de027a34e3eae90bed36dbe8973fa1625a79fe/image-20260603-090247.png?cb=955e05dd69f224d269d2f2046c8adf98) **Booking start** {{issue.customfield_10034.convertToTimeZone("Europe/Zurich").withHour(0).withMinute(0).withSecond(0).jiraDateTime}} Make sure you update your "Start time" custom field ID and the time zone of your resource **Booking end** {{issue.customfield_10035.convertToTimeZone("Europe/Zurich").withHour(23).withMinute(59).withSecond(59).jiraDateTime}} Make sure you update your "Start time" custom field ID and the time zone of your resource **Resource name** {{issue.customfield_10617.value}} Make sure you update your "Booking" custom field ID ### Action: Link work item to Link the second booking request to the first one. ![image-20260603-090545.png](https://booking.apwide.com/__attachments/a_24dfe6e6498ffd1a16e9add0616e8ec0073b0208a250696d0d25793bedea7bc6/image-20260603-090545.png?cb=ed01e4dd89a778a5deba80a091db17a5) **Link** {{createdJiraBooking.issueKey}} ### Branch: Linked work items Create a branch for the second booking request, so that we can access it. ![image-20260603-090944.png](https://booking.apwide.com/__attachments/a_59968f6e7f1d684d3f2a489c32933a0dbc058e79dd97758071c7637b3d6962fd/image-20260603-090944.png?cb=69705b7bfa43e7b0ab87a8378fb5233e) ### Action: Transition work item Force the approval of the second booking request, even though it conflicts with the first booking request. ![image-20260603-091118.png](https://booking.apwide.com/__attachments/a_5c51b56fde9c2dd0a2e3e4fe1eb9cf2700766b1f954e2fe266619713793d09bf/image-20260603-091118.png?cb=d6df4544279f605ed638bd4b9bbfe12c) ### Action: Delete work item links Remove the link that we created previously. If you have enabled "Link conflicts" in your Booking Flow, another link will be created automatically between the two booking requests. ![image-20260603-091228.png](https://booking.apwide.com/__attachments/a_5b65694147180635162a1e5d73fe7e557e265318a8fbcd5e9af494888575acc7/image-20260603-091228.png?cb=07663654b5cc453559d71beef7534905) *** ** * ** *** ## Need Assistance? For support with Jira Automation with Booking, reach out to our [++Customer Portal++](https://apwide.atlassian.net/servicedesk/customer/portal/1/group/1/create/1). --- language: "en" --- # Book parking spots for appointments When a customer books an appointment, they can specify how many parking spots they need. Parking bookings are created automatically and include a 30-minute buffer before and after the appointment. ![image-20260618-194153.png](https://booking.apwide.com/__attachments/a_fa20d7a549354b75a4cbc056b334201cc0b69607d9efe475c892db7390e8ae10/image-20260618-194153.png?cb=d313d628a24ba782c5b412d8974d167e) Example of a Customer Appointment JSM request *** ** * ** *** ## Requirements * **Advanced Edition** of Apwide Booking, which includes Automatic Resource Selection. * Booking Flow configured for parking spots. * JSM request configured for your Customer Appointments, using a **Single Select custom field** for the number of Parking Spots to be booked. * Access to **Jira Automation**. * Familiarity with creating **automation flows** and using **smart values**. *** ** * ** *** ## Configuration For this use case, we'll need three Jira Automation rules: 1. **Parking Spot Booking (Each)** - Create a Parking Spot booking request and decrement the number of parking spots remaining to be booked in an issue property. 2. **Parking Spot Booking (Start)** - When a new Customer Appointment request includes parking spots, trigger the first Jira Automation and add a comment to inform the customer that parking availability is being checked. 3. **Parking Spot Booking (Approval)** - Each time a Parking Spot booking request is approved or rejected, trigger the first Jira Automation and add a comment to the linked Customer Appointment request. *** ** * ** *** ## 1- Jira Automation: Parking Spot Booking (Each) Each time we trigger this automation flow, create a Parking Spot booking request and decrement the number of parking spots remaining to be booked in an issue property. **Enable flow-to-flow triggers** Since this flow is triggered by the first flow, make sure to select the "Check to allow other flow actions to trigger this flow" checkbox in the Flow details. ![image-20260710-093955.png](https://booking.apwide.com/__attachments/a_79d9b62b8325f0854c49a1e0742cdaf946ed4556b2f8511d160879d71af1df32/image-20260710-093955.png?cb=b9aa71c3d7adb869d694d76ad598eb3a) First Jira Automation Configuration ### Trigger: Incoming webhook The second and third Jira Automations will call this first Jira Automation via an incoming webhook. ![image-20260710-100224.png](https://booking.apwide.com/__attachments/a_338f8626cfa55640143493e47115c008782132a2b78d9b94667edf38ce7513e9/image-20260710-100224.png?cb=4e25f3fa05b2e84472f394345c6429a6) ### Condition: {{smart values}} condition We check if the **parking_spots_to_book** issue property is greater than **0**. ![image-20260618-201437.png](https://booking.apwide.com/__attachments/a_812821b13fe2b7b06e5a86a7b39a0526ac9fdab40a1d2e7c8d6e8d01e3b4eb45/image-20260618-201437.png?cb=2541df989b01f8b0bde04ba62bdd836e) **First value** {{issue.properties.parking_spots_to_book}} ### Action: Create Apwide Booking We create a Parking Spot booking with a randomly selected available resource and a 30-minute buffer before and after the appointment. ![image-20260618-201900.png](https://booking.apwide.com/__attachments/a_3173a0f9f43ee5e32f69aa3475c1f70763422926a3ba887468d001a6ce80f388/image-20260618-201900.png?cb=19386841ab29ca4bc89da48f82e04501) **Summary** Parking Spot Booking ({{#=}}{{issue."Parking Spots".value}} - {{issue.properties.parking_spots_to_book}} + 1{{/}}/{{issue."Parking Spots".value}}) **Booking start** {{issue.customfield_10156.minusMinutes(30)}} **Booking end** {{issue.customfield_10155.plusMinutes(30)}} ### Condition: If block We check if the booking was successfully created. ![image-20260618-202151.png](https://booking.apwide.com/__attachments/a_d2e15c009d2fc2969251f6e214321e61925f7c583aa1bc54ccc0336ca86830b7/image-20260618-202151.png?cb=bf3877e9e273d81740e19f60aa073870) **First value** {{createdJiraBooking.success}} ### Action: Link work items If the booking was successfully created, we link it to the current work item. ![image-20260618-202319.png](https://booking.apwide.com/__attachments/a_b486731329722807ef956cc81eeba28124b5f699683c7b73b01f8da731f4de14/image-20260618-202319.png?cb=2d04970e6b308c02e9da1335caeda113) **Linked work item** {{createdJiraBooking.issueKey}} ### Action: Set work item property If the booking is successfully created, we decrement the issue property by 1. ![image-20260618-202444.png](https://booking.apwide.com/__attachments/a_bef618abea4054edc4c3d489e59637cf3b6391aa1fc0290b576eaba7daaa1b5c/image-20260618-202444.png?cb=4ed9f425488ede047530c28cb2e77542) **Property key** parking_spots_to_book **Property value** {{issue.properties.parking_spots_to_book.minus(1)}} ### Condition: Else block If the booking was not successfully created. ![image-20260618-202706.png](https://booking.apwide.com/__attachments/a_86d3ca51239f4ef95118b4ca469b0ca6a0ba2367118e3e606429c2b756cbf498/image-20260618-202706.png?cb=d5272b14ab3f8fb820ee24d4532efc5a) ### Action: Comment on work item ![image-20260618-202816.png](https://booking.apwide.com/__attachments/a_329f615153df0bd8cd58cb3d90b0d29fd413db025d0dd2e1340cf236223ed322/image-20260618-202816.png?cb=b888dd38e2e2fda2c535d8286d646857) **Comment** Unfortunately, we could not book more parking spots for you. *From*: {{triggerIssue.customfield_10156.minusMinutes(30).convertToTimeZone("Europe/Zurich").format("EEE, dd MMM yyyy HH:mm z")}} *Until*: {{triggerIssue.customfield_10155.plusMinutes(30).convertToTimeZone("Europe/Zurich").format("EEE, dd MMM yyyy HH:mm z")}} Please contact the parking manager for assistance. ### Action: Set entity property ![image-20260618-202849.png](https://booking.apwide.com/__attachments/a_bf03fdf74c088c644f5da53de28ceef1f8a4e2f1e98af89136f5f26767e911c2/image-20260618-202849.png?cb=03813456f156ded209ba753597e2f54c) **Property key** parking_spots_to_book *** ** * ** *** ## 2- Jira Automation: Parking Spot Booking (Start) When a new Customer Appointment request includes parking spots, add a comment to inform the customer that parking availability is being checked. ![image-20260710-100907.png](https://booking.apwide.com/__attachments/a_8b4df85a6913ae26d26de34bebca1b46224b6cb7c25c2b5c0a96adb1f6432d5c/image-20260710-100907.png?cb=1993001410a469e465befffd4d5af2a7) Second Jira Automation Configuration ### Trigger: Work item created The flow will be triggered when the Customer Appointment request is created. ![image-20260618-195637.png](https://booking.apwide.com/__attachments/a_6b835c29851078fe6044520230d5f413af57861d711b938209a8db83c1fca02b/image-20260618-195637.png?cb=9638d1c35b9250e88dddf829937ca1cf) **JQL Example** project = BP and "Request Type" = "Customer Appointment" ### Condition: {{smart values}} condition We check if the **Parking Spots** field value is greater than **0**. ![image-20260618-195820.png](https://booking.apwide.com/__attachments/a_7d9af670036bba5f22405a0cb4efb3298310b26940357b3dd408e2b7874890a8/image-20260618-195820.png?cb=6a07e793464c7125399af9ffb826e66a) **First value** {{issue."Parking Spots".value}} ### Action: Set entity property We initialize an issue entity property with the number of parking spots to book. ![image-20260618-200126.png](https://booking.apwide.com/__attachments/a_a68e2779685d8d793a1aa2f7a21c4bfae51d4d45516e98a91172336647f56f39/image-20260618-200126.png?cb=765a792f3aa53471677d29cd59b41ff2) **Property key** parking_spots_to_book **Property value** {{issue."Parking Spots".value}} ### Action: Send web request ![image-20260710-100422.png](https://booking.apwide.com/__attachments/a_8acac59ebcdc195bafbf00ca4139c3b5b1e87c488094ddcb27fddcb5cad6b2d7/image-20260710-100422.png?cb=82f7eee93e5c17a818d8f4ef934ae0cb) **Web request URL** < Webhook URL of your first Jira Automation > **Custom data** { "issues": [ "{{issue.key}}" ] } **Header key** Content-type **Header value** application/json **Header key** X-Automation-Webhook-Token **Header value** < Secret of your first Jira Automation > ### Action: Comment on work item We add a comment on the work item, that will trigger the next Jira Automation. ![image-20260618-200348.png](https://booking.apwide.com/__attachments/a_16c401830a6b6296de9617ea37feed5e14312b0b8f8439f80fb77452f9ab8695/image-20260618-200348.png?cb=271e32efb80390440243469aa7edd27a) **Comment** Thank your for your appointment request. We are currently checking parking availability and will attempt to reserve {{issue."Parking Spots".value}} parking spot(s) for you. *** ** * ** *** ## 3- Jira Automation: Parking Spot Booking (Approval) Each time a Parking Spot booking request is approved or rejected, add a comment to the linked Customer Appointment request. ![image-20260710-101022.png](https://booking.apwide.com/__attachments/a_47ecd2231a8eea9cc9b7f9b74bdafbf45981e644f708ed7414599a87456d679a/image-20260710-101022.png?cb=d9eabf956d8ebe1ab97858fe40d272e2) Third Jira Automation Configuration ### Trigger: Work item transitioned The flow will be triggered when the Parking Spot Booking is approved or rejected. ![image-20260618-203031.png](https://booking.apwide.com/__attachments/a_6055c427f92ba7888bb9c5d8ef310f758795113f56c572e573519c6535baf528/image-20260618-203031.png?cb=ca2d66481647821990083ca779a78044) **JQL** project = BP and type = "Parking Spot Booking" ### Branch: Branch flow / related work items We create a branch for the Customer Appointment linked to the Parking Spot Booking. ![image-20260618-203252.png](https://booking.apwide.com/__attachments/a_0838840abf01ae4ca5c14773020da98272ebbad88462d5ec276a6e06091ab900/image-20260618-203252.png?cb=921c8f682d8a9bac8b393753eb8d0c86) ### Action: Send web request ![image-20260710-101114.png](https://booking.apwide.com/__attachments/a_c5384220b0fc2c5184d1ac21de1468f25ac24345d1da2615e7e5a735fc919cce/image-20260710-101114.png?cb=7ddda12966e8954b3ffc8ed42cab2a4e) **Web request URL** < Webhook URL of your first Jira Automation > **Custom data** { "issues": [ "{{issue.key}}" ] } **Header key** Content-type **Header value** application/json **Header key** X-Automation-Webhook-Token **Header value** < Secret of your first Jira Automation > ### Action: Comment on work item We add a comment to the Customer Appointment request, which triggers the creation of the next Parking Spot booking, if required. ![image-20260618-203430.png](https://booking.apwide.com/__attachments/a_16e72dafebda1e18f3d126aa2d6890b253c682be7311d88980833c93f29daac5/image-20260618-203430.png?cb=ebb7c2846020dde2cef292e506e141cd) *** ** * ** *** ## Need Assistance? For support with Jira Automation with Booking, reach out to our [++Customer Portal++](https://apwide.atlassian.net/servicedesk/customer/portal/1/group/1/create/1). --- language: "en" --- # Booking Flows **Booking Flows** are predefined configurations that allow you to book resources in Jira or JSM. Each **Booking Flow** includes a resource pool and a booking configuration. *** ** * ** *** ## Booking Flow Types ### Templates * **Meeting Room:** Reserve meeting rooms. * **Mobile Device:** Manage and reserve handheld devices. * **Desk:** Secure your workspace. * **Company Vehicle:** Book company vehicles promptly for business needs. * **Parking Slot:** Reserve parking spaces to save time and avoid hassle. * **Software License:** Reserve essential software licenses. * **Medical Equipment:** Book critical medical equipment without delay. * **VR Equipment:** Schedule virtual reality equipment bookings. * **Test Environment:** Use Golive to mange Environment and Deployment directly in Jira. * **Other Stuff:**Start from scratch with blank fields and no pre-filled resources. ### Custom * **Custom Flow:**Create a flow using your existing Jira space, issue type, fields and workflow. *** ** * ** *** ## Booking Flow Tabs Booking Flows offer different tabs for managing your bookings: ### List Tab Lists all resource reservations with filters: * **Start Date** * **End Date** * **Reporter** * **Resources** * **Statuses** ![image-20250227-132159.png](https://booking.apwide.com/__attachments/a_bf78eeb3c63531992facc89b897780307d27e787083f6b0f9f71b466cf79c554/image-20250227-132159.png?cb=d433fc5b432baa58cb6d81ea9cba5f50) Example of the Booking Flow List Tab ### Timeline Tab Shows all resource reservations in a timeline format. **Tips** Drag the timeline to navigate, and mouse scroll to zoom in/out. Click to book, and drag-and-drop existing bookings to reschedule them. ![Booking Timeline (1).gif](https://booking.apwide.com/__attachments/a_5c21a574ba83a7b743b4b116e0530083b2cdb2de51c13fe135175340f32979aa/Booking%20Timeline%20(1).gif?cb=fc54fc7116b02f695e04a95cf596b78e) Example of the Booking Flow Timeline Tab ### Resources Tab Lists all available resources within a Booking Flow. **Tip** Click **Update Resources** to add more items to the resource pool. ![image-20250227-132227.png](https://booking.apwide.com/__attachments/a_a7ec461ab4f2e2466ea6166eb0bfec0d446cef8ec35f4b52ee3fca807db67bf2/image-20250227-132227.png?cb=2724eed7b5c3db9f1231baa979b3c136) Example of the Booking Flow Resources Tab --- language: "en" --- # Booking Hub When you open **Apwide Booking** , the **Booking Hub** serves as your landing page, providing an overview of all your [Booking Flows](https://booking.apwide.com/doc/booking-flow.md). From here, you can: * Open *existing*Booking Flows * [Create *new* Booking Flows](https://booking.apwide.com/doc/creating-a-booking-flow.md) **Important** You must be a **Jira Administrator** to create Booking Flows. [More information about Permissions](https://booking.apwide.com/doc/permissions.md) **Info** If you cannot view Booking Flows, contact your **Jira Administrator** for assistance. ![image-20250120-215402.png](https://booking.apwide.com/__attachments/a_d0fc6a5bc12c51c8296379fea27e813dcf943e1b241e952bf148647231146bfd/image-20250120-215402.png?cb=9a2b0e447e2225cdec58706ee6cbf443) Booking Hub configured with 3 Booking Flows *** ** * ** *** ## Accessing the Booking Hub You can access the Booking Hub in two ways: ### 1. From the Jira Apps Menu #### Requirements * Apwide Booking must be installed. For instructions, refer to the [Get Started](https://booking.apwide.com/doc/get-started.md) documentation. #### Steps 1. In Jira, click **Apps** in the main navigation menu. 2. From the drop-down menu, select **Booking Hub**. ### 2. Directly from a Jira Space #### Requirements * The Jira space must have at least one active [Booking Flow](https://booking.apwide.com/doc/booking-flow.md). #### Steps 1. In Jira, open the desired space. 2. Locate and click the **Booking** tab. The active Booking Flows will display and function as expected. **Tip** If you don't see the Booking tab, click **More** at the top-right of the space menu. ![image-20250528-201500.png](https://booking.apwide.com/__attachments/a_708d701f2249e15ddab03985ebbf991514f8005eca1fb0b6f368528d91d945d0/image-20250528-201500.png?cb=2979562f825dd00796e9545a759907ad) --- language: "en" --- # Change Logs ## 11.10 (2026-06-24) ### Booking Field Inline Editing New Feature In the standard booking flow, the Booking field is read-only on the Jira work item. Bookings are updated through a reschedule transition, which displays the time selection interface and applies the Booking Flow rules. Some use cases require more flexibility, so the Booking field can now be edited directly from the Jira work item's Edit screen. Add the field to the relevant Edit screen to allow users to change the selected resource. When Resource Capacity is enabled for the Booking Flow, users can also update the requested quantity. ![image-20260624-150735.png](https://booking.apwide.com/__attachments/a_b339425c1bfa21161f052146ddbd70135b910372456da6aaf98db554f1189a52/image-20260624-150735.png?cb=fbbe2d7213189de2585b41fdc27ccad5) Booking field inline editing Changes to the Start time, End time, or Booking field automatically trigger conflict detection. The result is displayed in the Booking Activity Tab. You can use Jira Automation to define what happens after these changes. For example, you can automatically transition the work item to **To Review** so that the updated booking can be approved again. improvement **Clearer availability messages** - Availability messages now distinguish between "*Insufficient availability"* when Resource Capacity is enabled and "*Resource unavailable"* when it is not. We have also restored the green confirmation banner when the selected resource is available for the requested time range and quantity. bugfix Fixed an issue where the Booking field did not render correctly in the Time Slots booking experience when the Booking Flow contained only one resource. *** ** * ** *** ## 11.9 (2026-06-22) ### Multi-resource Booking New Feature advanced We've introduced Multi-resource Booking, allowing users to reserve several related resources from a single booking request. Administrators can now configure additional resource types for a Booking Flow. For example, when booking a studio, users can also reserve a control room and a video camera as part of the same request. ![image-20260618-145354.png](https://booking.apwide.com/__attachments/a_35376aa4a1fa5197a8be523e56ddd5d684fc1d2820b45d67523477e7af241e01/image-20260618-145354.png?cb=ad455690b3909182ab2aa722f1644019) Additional resources configuration in Booking Flow edition When the request is submitted, Apwide Booking automatically creates linked booking requests for each selected additional resource. All bookings share the same start and end date and remain connected through Jira issue links. ![image-20260618-145536.png](https://booking.apwide.com/__attachments/a_69d7c096a8f3d9d6bae979d34c75c1818cf5b3b9271347944f30986cd1ba1f57/image-20260618-145536.png?cb=9d3780e3a60e8ff6d364d01d649def75) Additional booking requests linked to the main one improvement We've implemented a workaround for the Atlassian issue [ECO-1568](https://jira.atlassian.com/browse/ECO-1568). When Apwide Booking cannot determine the app edition, the Automation actions temporarily assume the Advanced edition is available. As a result, the Automatic Resource Selection capability can now be used in Jira Automation even when the edition check cannot be completed. This behavior will remain in place until Atlassian resolves the underlying issue. improvement Compatibility with the recent [Jira field configuration improvements](https://developer.atlassian.com/changelog/#CHANGE-3019). bugfix Fixed an issue where time and duration options were displayed on two lines, instead of one. *** ** * ** *** ## 11.8 (2026-06-18) No changes. Redeploy requested by Atlassian in order to fix a Jira permission bug. *** ** * ** *** ## 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 no longer select a resource during booking creation. Instead, Apwide Booking automatically assigns a random resource that is available for the selected date and time range. In the Time Selection and Time Slots booking experiences, the resource field is hidden when automatic selection is enabled. The Resource Availability booking experience is not compatible with this mode, as it requires users to select a resource before viewing availability. This capability is also supported by the [**Create Apwide Booking**](https://booking.apwide.com/doc/action-create-apwide-booking.md) automation action. If the Resource field is left empty, a random available resource is automatically selected. ![image-20260604-145052.png](https://booking.apwide.com/__attachments/a_7c0237fccef7926a42465496556f71c80617bdfb1438d9da7c4430d6a33cf33e/image-20260604-145052.png?cb=f8106802c05868bf9fd017f5d8072916) Resource selection parameter in the Edit Booking Flow ![image-20260604-122249.png](https://booking.apwide.com/__attachments/a_ab67b1df268f5bf75afd3d91d36620872c02f2085fccc25113a15beaa368cd40/image-20260604-122249.png?cb=ffe78aa9f2aa91fc18cedac1be2e0c00) JSM Request with Automatic Parking Slot Selection ### 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. ![image-20260604-145453.png](https://booking.apwide.com/__attachments/a_a584b6dc4802d2725b22ce4aff79455c8b2ec7a15ea71a99cd63dd844a3aeee2/image-20260604-145453.png?cb=e4beb480822458fba3adc4cf5a089b0b) Booking Activity Tab in the Jira work items 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++](https://booking.apwide.com/doc/managing-booking-flows.md) ![image-20260521-094743.png](https://booking.apwide.com/__attachments/a_90eaba078832d2e0abb5859ac1cb94633796f9ff035046aac331ad1b3eeb74d0/image-20260521-094743.png?cb=22a9a3f6e1b96894079d441bbac681bc) Quantity selector in the Booking field ![image-20260521-095544.png](https://booking.apwide.com/__attachments/a_7d99313973d2202d433a6355796891cd1472dd50f059bb35e572a6c5471e6f27/image-20260521-095544.png?cb=0cc66caf09913339e543aca4472cf594) Timeline with enabled capacity ![image-20260521-094059.png](https://booking.apwide.com/__attachments/a_151849103ceb360309497f4a687e4b2943ba34857f63916e9096532aa4017fdc/image-20260521-094059.png?cb=c30b3fd3b7ab0491221ec104c1063a77) Selection of the Assets attribute storing the resource capacity 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. ![image-20260521-091336.png](https://booking.apwide.com/__attachments/a_ecc03a3b24a2a86697f0b26f95171e15003d8fcbb807fef01e5f028a8cf39709/image-20260521-091336.png?cb=dc3019d652b3445042b623ef1d83bc0d) Workflow tab in Edit Booking Flow 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](https://community.atlassian.com/forums/Jira-Cloud-Admins-articles/Say-goodbye-to-field-configuration-schemes-and-hello-to-the/ba-p/3160315) 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) **Security fixes** We've fixed various security improvements, including a critical issue where non-admin users could delete a Booking Flow. If you are not yet on version 11.x, we strongly recommend upgrading to the latest version. improvement Improved conflict visualization in both *Resource Availability* and *Time Selection* booking experiences. improvement Improved date range visualization in the *Resource Availability* calendar. ![image-20260423-071742.png](https://booking.apwide.com/__attachments/a_2fbfea28875f17f282d1b4a2f9f09feda9786716557cfa792ed73b16f0640d56/image-20260423-071742.png?cb=1648365ab32542e62d5b90d1d940e497) Better handling of multi-day bookings 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++](https://booking.apwide.com/doc/permissions.md) ![image-20260415-111612.png](https://booking.apwide.com/__attachments/a_742bc7ca6e41dfd7b1ca2c1aa16adda73d122217239fad546c67b5c778a704c1/image-20260415-111612.png?cb=eb26b96e3cdf3cd5c49b9051ef4d7a5b) Permissions Tab 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++](https://booking.apwide.com/doc/customize-the-booking-experience.md) ![image-20260409-125225.png](https://booking.apwide.com/__attachments/a_a27e46bd68ee60bdcf123ff76a8914db6b1961c659f44bfde946e94e17807831/image-20260409-125225.png?cb=3d5c85f1ab54f652d8296557e5de3a54) Slot Duration Picker 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) **Manual Upgrade Required** Version 11.0 introduces Assets and Rovo permissions and requires manual approval. To complete the upgrade, a **Jira Administrator** must go to **Manage Apps** and click **Update**. ### 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](https://booking.apwide.com/doc/customize-the-booking-experience.md) ![image-20260320-112842.png](https://booking.apwide.com/__attachments/a_ca472f7e7d41642a5e57add265a078573e3c1cb02205348dbe1c8b286289ac3f/image-20260320-112842.png?cb=b4ee8d68b1ef057ada851da14c5f4a55) Resource Availability booking experience on the JSM Portal ### 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](https://booking.apwide.com/doc/rovo-skills.md) ![BookingRovoSkills.png](https://booking.apwide.com/__attachments/a_e1c5e950cad29b3fa2f2035b8c0eef872379eda3d08d23cdd0b45bad85dcdee8/BookingRovoSkills.png?cb=c42d8fff1edaf3ca45a45e1c87e9a651) Selecting Rovo Skills in Atlassian Studio ### 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](https://booking.apwide.com/doc/action-create-apwide-booking.md) ![CreateApwideBooking.png](https://booking.apwide.com/__attachments/a_1b0668339610e88ee103adfc7eaf06582c914b903ec616fb8e42a28f13d0ef3a/CreateApwideBooking.png?cb=dd302c6726e73166ad87c401ec102cd6) Create Apwide Booking action in Jira Automation 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. ![07d6bdb1-6abb-4e2c-b398-c54f0cc4415a.png](https://booking.apwide.com/__attachments/a_5192ceda206152614247251db3e2e568882ab59141bf8a7a5db672b04aa72066/07d6bdb1-6abb-4e2c-b398-c54f0cc4415a.png?cb=0a2a9db9cdaf1c6e318197138fbd8e6d) Example of banner inviting Jira Administrators to 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) **Manual Upgrade Required** Version 10.0 introduces Jira Assets filtering and requires manual approval. To complete the upgrade, a **Jira Administrator** must go to **Manage Apps** and click **Update**. ### 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. ![image-20260226-172627.png](https://booking.apwide.com/__attachments/a_ad9f6fa0f93ee3612b97043d42281606f43a2260c5f6094353d74dce2721d10e/image-20260226-172627.png?cb=3626e915a9db747efb9eb76ef98a8b2c) Filter your Timelines by Assets Attributes ![image-20260226-173242.png](https://booking.apwide.com/__attachments/a_9883b01baef97b13516f10534f1f81a8d83fd7a903cdbfad51a97a8597eb7c48/image-20260226-173242.png?cb=7290779635b072b9df094499cfe3c5a9) Filter your resources when booking *** ** * ** *** ## 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](https://booking.apwide.com/doc/customize-the-booking-experience.md) 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](https://booking.apwide.com/doc/creating-a-booking-flow.md) documentation. ![image-20260129-131357.png](https://booking.apwide.com/__attachments/a_44714717837c9067383e309fe01b5c7a23a25cc3acc066c37097646cdaba0b54/image-20260129-131357.png?cb=763e3ed75ca9179af7ce53ea04ea0812) Booking Flow creation wizard *** ** * ** *** ## 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. ![image-20260112-103753.png](https://booking.apwide.com/__attachments/a_c82d0d2a457437d60b2849d972b93c19e065d38fa4bdbce77f6213e624f02bce/image-20260112-103753.png?cb=e7e8a686cf28bd4ad0c45ae2d6833417) Example of maximum duration improvement Improved the [Rovo Agent](https://booking.apwide.com/doc/rovo-agent.md) 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**. *** ** * ** *** For previous change logs, refer to [Change Logs 2025](https://booking.apwide.com/doc/change-logs-2025.md) --- language: "en" --- # Change Logs 2025 For the latest Change Logs, refer to [Change Logs](https://booking.apwide.com/doc/change-logs.md) ## 9.5 (2025-12-22) New feature Added buttons to open the [Rovo Agent](https://booking.apwide.com/doc/rovo-agent.md) from the **Booking Hub** and **Booking Flows**. These buttons are available only when Rovo is enabled on your Jira instance. ![image-20251222-145404.png](https://booking.apwide.com/__attachments/a_10a3c7f518f65f26a6029296b84eec8bfbb4e2328f88ca579d2b49006c3462b9/image-20251222-145404.png?cb=8b373f202d201e7b1577f489fe87a743) New banner in the Booking Hub improvement Improved [Rovo Agent](https://booking.apwide.com/doc/rovo-agent.md) behavior to guide users to the **Booking Flow** when time slot enforcement is required. improvement Added a direct link in **Booking Flows** to open the related JSM request, when applicable. ![image-20251222-145506.png](https://booking.apwide.com/__attachments/a_a703163e15b5045cf0fab68c97293fa26de8f9092acb6d5bdb75ecd31eb9a57c/image-20251222-145506.png?cb=f022984c69b232eaef20cd044e6e2a03) New "Book with Rovo" button and "Open in JSM" link in the Booking Flows improvement Introduced a warning message in the **Timeline** and **Resources** tabs when not all resources are displayed. bugfix Fixed an issue where some suggestions were missing when resources were stored as **Jira Assets**. bugfix Fixed an issue where the **Cancel** link did not work correctly when deleting a Booking Flow. *** ** * ** *** ## 9.4 (2025-11-27) bugfix Fixed an issue where the trigger status was not required when auto-approval and conflicting request linking were both disabled. *** ** * ** *** ## 9.3 (2025-11-26) improvement When editing a Booking Flow, display only the active workflow statuses in the status fields of the Approval tab. bugfix Fixed an issue where the resource selection dropdown occasionally failed to list all assets returned from Jira Assets. *** ** * ** *** ## 9.2 (2025-11-19) New feature Added the new **Edit Apwide Booking** Jira Automation action that updates booking fields, including start date, end date, and resource. This action is powered by a new Jira beta capability. For details, refer to the [Jira Automation](https://booking.apwide.com/doc/jira-automation.md) documentation. ![image-20251119-115057.png](https://booking.apwide.com/__attachments/a_1f517467d6bee7808bcb20109ad5ff1fd329e79bc579252d9cc033680278ec0d/image-20251119-115057.png?cb=3ab0df4dbb2a10c9a6f395fca1342a28) Jira Automation Action improvement Updated the Booking Flow field order to **Booking** , **Start** **time** , and **End time**, and moved the warning banner for unsupported UI modifications to the end of the Booking field. ![image-20251119-115200.png](https://booking.apwide.com/__attachments/a_2f47b1f68df3962492d2cb4fd0c827e2ef0bd4fb9fb79279f1039e309d6e15ce/image-20251119-115200.png?cb=45432103ba1cc854f955cfd15810a3b3) Field order applied to new Booking Flows *** ** * ** *** ## 9.1 (2025-11-12) improvement Booking custom fields are now fully supported in JSM, and Jira Administrators are requested to add the Booking field in their existing JSM requests (on-screen help is displayed on the portal). The JSM panel component is now deprecated and will be removed in a future version. ![image-20251119-115358.png](https://booking.apwide.com/__attachments/a_07709df0972dc160e26d852258de2396a6fc0f29cb71249587a75996940fa406/image-20251119-115358.png?cb=8446d649e1390bff266a2711248b3313) Warning message displayed for Jira Administrators on the JSM requests *** ** * ** *** ## 9.0 (2025-11-06) **Manual Upgrade Required** Version 9.0 introduces analytics and requires manual approval. To complete the upgrade, a **Jira Administrator** must go to **Manage Apps** and click **Update**. improvement Added a new **Canceled** status with a **Cancel Booking** transition from all statuses in workflows generated from Booking Flow templates. This transition can also be enabled in JSM, allowing portal users to cancel their bookings directly when needed. improvement When creating a new Jira Space from a Booking Flow template, we now remove unused work types (like "Task") to keep your space cleaner and more focused. improvement Booking-related fields have been moved to the right-hand column when viewing booking requests in the JSM portal. improvement A new permission issue warning banner is now displayed during Booking Flow creation. This helps alert Jira administrators immediately if there's a problem with the Booking App installation. improvement The time zone display has been moved closer to the **Date** and **Duration** fields across all booking screens for better context and readability. improvement Implemented product analytics using the Accoil platform. improvement Users with an expired license will now have their access to the Booking App blocked. improvement Updated the app's terminology to align with Atlassian's new naming convention, now using **Space** instead of "Project." bugfix In JSM, we fixed an issue that could cause booking information to display prematurely. It is now prevented from displaying until the Booking App has properly set the values. bugfix The timeline is now forced to refresh automatically whenever resources are updated, ensuring you always see the most current schedule. *** ** * ** *** ## 8.8 (2025-10-05) improvement Enhanced the user experience by providing better feedback when changing months. improvement Added the ability to edit Booking Flows directly from the Booking project page. improvement Added the ability to define the Booking Experience when creating a new Booking Flow. bugfix Fixed an issue where Booking Flow creation would fail if Jira Software was not installed. *** ** * ** *** ## 8.7 (2025-09-26) bugfix Fixed an infinite loop affecting customers in *negative* GMT time zones (e.g., the Americas) when using **Time slots**. This issue impacted all Booking Flows on computers configured with those time zones. *** ** * ** *** ## 8.6 (2025-09-25) improvement The app now redirects users to the **Booking Hub** if a direct URL points to an unknown flow. *** ** * ** *** ## 8.5 (2025-09-24) bugfix Fixed an issue in **Time slots** where the earliest bookable date in a custom date range did not respect the minimum notice time. *** ** * ** *** ## 8.4 (2025-09-24) bugfix Fixed a problem that prevented saving when creating a Booking Flow from scratch. *** ** * ** *** ## 8.3 (2025-09-24) bugfix Fixed an issue that prevented the creation of the first Booking Flow. *** ** * ** *** ## 8.2 (2025-09-23) bugfix Improved stability and loading of Booking Flows so broken flows do not affect the app. *** ** * ** *** ## 8.1 (2025-09-22) bugfix Fixed a bug that could leave the app stuck showing a loading spinner. *** ** * ** *** ## 8.0 (2025-09-19) **Manual Upgrade Required** Version **8.0** includes a new permission that allows creating a JSM request when setting up a new Booking Flow in Jira Service projects. A **Jira Administrator** must go to **Manage Apps** and click **Update** to grant the new permission. improvement When creating a booking flow in a JSM project, the corresponding request type is now created automatically. By default, this request type remains hidden, and you must remove the Booking field manually. For details, refer to the [Create a JSM Request](https://booking.apwide.com/doc/creating-a-jsm-request.md) ddoumentation. improvement Added a **Save**button when adding availability windows or editing custom date ranges. improvement In the timeline of a Booking Flow configured with **Time Slots**, users can now click an existing booking to reschedule it. *** ** * ** *** ## 7.18 (2025-10-02) improvement Added a banner to encourage Booking App upgrade to the latest version. *** ** * ** *** ## 7.17 (2025-09-18) improvement Improved availability window configuration in **Time Slots**. bugfix Fixed an issue in **Time Slots**that would display a spinner infinitely with specific open period configurations. bugfix Fixed several usability issues in the **Custom Configuration**screen. *** ** * ** *** ## 7.16 (2025-09-16) improvement In **Jira Service Management**, a console message may appear if the app cannot connect to the Service Desk REST API. This issue affects some Jira instances and has already been reported to Atlassian. If you encounter it, please contact Atlassian Support. ![image-20250916-142852.png](https://booking.apwide.com/__attachments/a_1abb1c8a31b289044787c1316cf0b9f6b3cfa6ef0f6caee77381eecdf563f93a/image-20250916-142852.png?cb=45820fb5643062fa6f99152193646708) Message in the console when access to JSM is not allowed to Booking *** ** * ** *** ## 7.15 (2025-09-15) improvement In **Jira Service Management** , the loading process for the **Time Slots**booking experience has been improved. bugfix In **Jira Service Management**, submissions are now blocked until the panel is fully loaded and the configuration is fetched. This prevents users from submitting a request before the panel is ready. *** ** * ** *** ## 7.14 (2025-09-10) improvement In the **Time** **Slots** flow, users can now open the **Booking** dialog by clicking directly on the timeline. improvement Improved the loading sequence for the **Time Slots** booking experience. improvement The timeline's default zoom level now adapts to the configured duration: Slot duration for the **Time Slots** booking flow, and default **Duration** for other flows. improvement When converting a Booking Experience to **Time Slots**, the resource's timezone is set to the timezone of the user performing the conversion. *** ** * ** *** ## 7.13 (2025-09-03) bugfix Fixed an issue in the **Time Slots** booking experience where configured confirmed status IDs were ignored when calculating available slots. *** ** * ** *** ## 7.12 (2025-09-03) improvement In the **Time Slots** booking experience, the resource selector is now hidden if the **Booking Flow** resource pool contains only one item. improvement The **Reschedule** action in the **Time Slots** booking experience now pre-fills existing values. *** ** * ** *** ## 7.11 (2025-08-28) bugfix In Jira Service Management, the error message on the **Resource** field now disappears once you select a value. Previously, it stayed visible but did not block request submission. *** ** * ** *** ## 7.10 (2025-08-27) improvement Jira Service Management now shows a warning if no resource is selected within 10 seconds. This applies to *all booking experiences* except **Time Slots**. bugfix Fixed an issue that stopped the **Time Slots** booking option from working for Jira Service Management Portal users. *** ** * ** *** ## 7.9 (2025-08-26) improvement Jira Service Management now shows a warning if no slot or resource is selected within 10 seconds when using the **Time Slots**booking experience. bugfix Fixed display issues in **Time Slots** calendars. bugfix Fixed an issue where the old configuration appeared briefly when saving a new one. *** ** * ** *** ## 7.8 (2025-08-26) bugfix Fixed an issue that blocked updates to the resource list. *** ** * ** *** ## 7.7 (2025-08-22) improvement In the **Time Slots** booking experience, unavailable slots are now shown as *disabled* instead of being hidden. improvement The resource type warning now appears only when **Jira Assets** is installed, since resource type switching is only supported in that case. bugfix Fixed an issue where booking slots were displayed before the defined custom range start date. bugfix Fixed an issue in the **Booking Flow** configuration where read-only fields were editable by non-Jira administrators. *** ** * ** *** ## 7.6 (2025-08-21) improvement **Booking Experiences** ![image-20250826-102019.png](https://booking.apwide.com/__attachments/a_3689c0d77b08189cb7b49c8a1032131ecd1b13d4f99d32f2b4ee086708702f8b/image-20250826-102019.png?cb=83e0488c896082abe87bc5537fd0d922) Time Slots Booking Experience You can now choose between **4 booking experiences** in the **Availability** tab of your Booking Flow configuration: * **Start Time + Duration** * **Start Time + End Time** * **Start Time + Duration + End Time** * **Time Slots (beta)** The first three options let you control how start time, end time, and duration fields are displayed. You can also set: * A **default start time** (e.g., tomorrow at 08:00) * A **default duration** (e.g., 45 minutes) * A custom **duration field label** (useful for localization) **New Time Slots** The new **Time Slots** experience requires users to book from pre-defined time slots. It offers flexible configuration options, including: * Resource timezone * Availability windows * Duration * Rolling period or custom date range * Minimum notice time * Start time increment ![image-20250820-160405.png](https://booking.apwide.com/__attachments/a_7e0e5937110abc8c0e7c55eb9969132f6148ea8e3bd99218d8ab56991afafeef/image-20250820-160405.png?cb=bb294d02347e51d7193605ab49f8837f) Time Slots Booking Experience **Time Slots** apply to all resources in the Booking Flow. For per-resource availability, you can either: * Use **Jira Automation** to create placeholders for unavailable times (for recurring cases), or * Create separate **Booking Flows** for different resource groups. For setup instructions, refer to the [Customize the Booking Experience](https://booking.apwide.com/doc/customize-the-booking-experience.md) documentation. bugfix Fixed an issue that prevented the [Rovo Agent](https://booking.apwide.com/doc/rovo-agent.md) from retrieving resources from Booking Flows. *** ** * ** *** ## 7.5 (2025-08-11) bugfix **(JSM only)** Enhance error management when facing permission issues with Jira Servicedesk. *** ** * ** *** ## 7.4 (2025-07-10) bugfix **(JSM only)** Reverted to using a panel on the portal creation page. Forge custom fields are *not* *yet*supported for portal and anonymous users. *** ** * ** *** ## 7.3 (2025-07-08) bugfix Fixed an issue that prevented creating the first **Booking Flow** using a template when *start* and *end* custom fields were included. *** ** * ** *** ## 7.2 (2025-07-07) bugfix Fixed an issue where accentuated characters caused errors during **Booking Flow** creation. *** ** * ** *** ## 7.1 (2025-06-27) bugfix **(Visual adjustment)**Added a short delay to prevent valid resources from briefly appearing as invalid. *** ** * ** *** ## 7.0 (2025-06-25) **Manual Upgrade Required** Version **7.0** includes a new permission for Jira Assets. A **Jira Administrator** must go to **Manage Apps** and click **Update** to grant the new permission. improvement **Flexible Resource Pool Management** You can now choose how to manage your resource pool in Booking Flows: * Connect to **Jira Assets** using AQL queries (available for JSM Premium). * Manage resources directly in the **Booking App**, without relying on custom fields. This flexibility lets you structure resources based on your specific needs. ![image-20250625-081903.png](https://booking.apwide.com/__attachments/a_08f37a4c504bc84e7332583cafcd41591dbd14d740153ea6e9fb91d51af02461/image-20250625-081903.png?cb=4cf7effe9dd6910610e4cf6fc6e2209e) Booking Flow creation screen **Custom Field Change** Resource fields have moved from Jira's single-select custom field to a **Forge-based** custom field. * **What's better**: More flexible resource display. * **Limitations** : Currently, Forge fields **can't be used** in Jira statistics gadgets or JSM Forms. We're actively exploring improvements and would love your input. [Book a short call](https://meetings.hubspot.com/david-at-apwide) with our team if this impacts you. Your feedback matters! improvement **Smart Availability Suggestions in Native Jira Screens** Previously, resource availability suggestions were only shown in the Booking App's schedule and reschedule screens. With this update, you can now access the same smart suggestions directly from native Jira screens, including: * **Issue creation screens** * **Transition screens** This makes it easier to schedule or reschedule resources at the right time---without leaving Jira. ![image-20250625-082047.png](https://booking.apwide.com/__attachments/a_bc6a81eb253c8a490eb5d6d02d568e57d0f20d1109d355d78bb7af2cf55b075e/image-20250625-082047.png?cb=cd7befb1fcc993e1e66812aa90e36f2b) Jira Transition Screen with smart booking suggestions **Duplicate Date Fields in Some Jira Screens** Smart availability suggestions now work on most native Jira screens. However, due to current Jira limitations, you may see **duplicate Start/End date fields** on the following screens: * Issue creation screen in **JSM service projects** * Transition screens in **JSM service projects** * Transition screens in **business projects** Always use the **fields under the yellow "Booking" banner**. These are powered by the Booking App. Ignore the original Jira Start/End fields. ![image-20250625-082247.png](https://booking.apwide.com/__attachments/a_51b686319f358057f4356c596259300c05afd09e2e0e794f22fea4cbad399cb9/image-20250625-082247.png?cb=c3ace453c7312993e191f4f65ff655dc) For the best experience, use **Jira Software projects**. These are now the default when creating new projects from Booking Flows templates. improvement Improved **Booking Flow** editor with clearer button labels and a discard warning for unsaved changes. bugfix Removed the **Booking** header from the JSM portal when not linked to an active Booking Flow. *** ** * ** *** ## 6.1 (2025-05-28) bugfix Fixed a crash that occurred when selecting a Jira project while creating a **Custom Flow** template. bugfix Removed unnecessary error messages ("booking config") from JSM requests that aren't linked to a Booking Flow. *** ** * ** *** ## 6.0 (2025-05-21) **Manual Upgrade Required** Version 6.0 includes a new permission to write application properties. A Jira Administrator must go to **Manage Apps** and click **Update** to grant the new permission. improvement A **Project Page** is now available in every project with an active Booking Flow. You can access it from the left-hand menu or in the top navigation bar (under **More**, if there are many tabs). **Info** For existing flows, the tab may take up to **24 hours** to appear after upgrading. ![image-20250521-122758.png](https://booking.apwide.com/__attachments/a_91f6b5da3451130c491009835d710fd9f8aac10f61b1ba0dacec98b7c6ca719b/image-20250521-122758.png?cb=e028c80979fbd5978d822e7b9d361817) Booking Project Page improvement **Notification messages** , such as those shown after updating a Booking Flow, now appear in **modals** to ensure they are clearly visible and not missed. bugfix Fixed the **Create** button in the Booking Flow Template form, which remained disabled until a change was made. bugfix The **Statuses** filter now correctly displays available statuses. bugfix Drag-and-drop now works as expected, even when many events are displayed on the Timeline. *** ** * ** *** ## 5.8 (2025-05-15) improvement When creating a Booking Flow from a template, you'll now see the following fields: * **Name**: Name of your new flow. * **Description**: Description of your new flow. * **Resource field name**: Name of the new select list custom field listing your resources. * **Work type name**: Name of the new work item (issue type) used to book resources. ![image-20250515-093006.png](https://booking.apwide.com/__attachments/a_a22b290fb15d0d7dd22e144f52e31d74a59a1b094f727b013904a3051edff916/image-20250515-093006.png?cb=b241d5dfc51e7e1c2266147a296f9c12) More possibilities to create a bespoke Booking Flow improvement A new **Other Stuff** template is available. It includes empty fields and no default resources, making it ideal for starting from scratch. *** ** * ** *** ## 5.6 \& 5.7 (2025-05-14) **Jira Service Management:** bugfix The creation panel now appears for anonymous users. bugfix Improved conflict checks by ensuring the query considers all relevant tickets. *** ** * ** *** ## 5.4 \& 5.5 (2025-05-13) improvement Resolved minor user experience glitches. bugfix Our **Rovo Agent**now returns a valid URL for the created booking. bugfix Fixed an issue where start and end date validation failed in specific scenarios. bugfix Fixed an error when retrieving the **JSM** configuration. *** ** * ** *** ## 5.3 (2025-04-15) improvement Pressing **Enter** now speeds up the initial creation of the resources pool when starting a new **Booking Flow**. improvement Labels for deleting a **Booking Flow**have been clarified for better understanding. bugfix Project selection is now limited to company-wide projects to avoid incorrect assignments. *** ** * ** *** ## 5.2 (2025-04-10) bugfix Resolved an issue where the **Booking Creation** panel remained active when adding the **JSM Creation** panel, even on forms not related to bookings. The panel now behaves as expected and stays disabled when not applicable. *** ** * ** *** ## 5.1 (2025-04-08) improvement Custom field names are now displayed in forms, making them clearer and fully aligned with your Jira configuration. *** ** * ** *** ## 5.0 (2025-04-03) **Manual Upgrade Required** Version 5.0 includes a new **JSM** permission and requires manual approval. A Jira Administrator must go to **Manage Apps** and click **Update** to grant the new permission. improvement We've hidden the **Booking** activity tab for Jira work items that are not part of any **Booking Flow**. improvement Resource suggestions and conflict detection are now available on the **Jira Service Management Portal** . For detailed instructions, refer to the [Creating a JSM Request](https://booking.apwide.com/doc/creating-a-jsm-request.md) documentation. ![image-20250402-163112.png](https://booking.apwide.com/__attachments/a_9ab1446e4c22e5be2edc71adb78b0daf95d29414da1f85d00096958716beeb5c/image-20250402-163112.png?cb=ab66fad389143019c22c42b7f4ca6315) Suggestions in the JSM Requests *** ** * ** *** ## 4.8 (2025-04-01) bugfix Fixed an issue with the **Duration**selection. *** ** * ** *** ## 4.7 (2025-03-27) improvement Added a **Duration** field to simplify resource booking. Now, after selecting a **Start Date**, you can either: * Choose an **End Date**, and the system will calculate the duration automatically. * Enter a **Duration**, and the system will set the end date accordingly. ![Duration Field.gif](https://booking.apwide.com/__attachments/a_2048e1d11d0a649ba51f4ac226d995a240565a7934fe4e8714cc709ad864b89b/Duration%20Field.gif?cb=bab4f8bfa4d69b421fa55986b59a4ffa) *** ** * ** *** ## 4.6 (2025-03-20) improvement When creating a **Booking Flow**from a template, you can now select an existing Jira project or create a new one. ![image-20250320-132817.png](https://booking.apwide.com/__attachments/a_85b6b9e2392fff2ffdcdd45c589edf890411e7ac2649d892d83deca9f73e99ff/image-20250320-132817.png?cb=230112ae0608e16eea5bcfd20d8a2e6c) Booking Flow creation *** ** * ** *** ## 4.5 (2025-03-17) improvement You no longer need to specify a summary when booking with the **Rovo Agent**. bugfix Fixed an issue where draft workflow schemes caused failures when creating a Booking Flow from a template. These drafts are now automatically deleted. bugfix Fixed an issue where the **Rovo Agent**would not always return the link to the booking request work item. *** ** * ** *** ## 4.4 (2025-03-12) improvement Added a colorful Booking icon to the Jira **Apps** menu, for better visibility. bugfix Fixed an issue where the creation of a **Booking Flow** failed at the final step on some Jira instances. *** ** * ** *** ## 4.1, 4.2, 4.3 (2025-03-11) improvement Updated the **Reschedule** modal title to include a direct link to the Jira work item. *** ** * ** *** ## 4.0 (2025-02-26) **Manual Upgrade Required** Version 4.0 includes a new permission and requires manual approval. A Jira Administrator must go to **Manage Apps** and click **Update** to grant the new permission. ![Booking Timeline (1).gif](https://booking.apwide.com/__attachments/a_aa6e4f25a6a2ac8dc7b1a0b9eb6ee1a3a930832f2d6cca9d74cade1e2dd0519f/Booking%20Timeline%20(1).gif?cb=fc54fc7116b02f695e04a95cf596b78e) Timeline view for easy booking improvement Introduced a **Timeline**tab to help you visualize, schedule, and reschedule bookings bugfix The cursor now automatically focuses on the **Resource Name** field when adding a new resource in the **Quick Setup**. *** ** * ** *** ## 3.11 (2025-02-19) bugfix Added error message when transitions are not found when rescheduling. *** ** * ** *** ## 3.10 (2025-02-11) improvement Improved the flow for adding resources in **Quick Setup**. bugfix Fixed an issue where unprivileged users could not see the booking table. bugfix Added a missing permission check for **Quick Setup** steps. *** ** * ** *** ## 3.9 (2025-02-06) improvement Improved speed for suggestion and conflict prediction when booking or rescheduling. bugfix Ensured the correct timezone is used and displayed to users. *** ** * ** *** ## 3.8 (2025-01-31) bugfix Fixed a issue with the reschedule modal not being up to date after rescheduling. *** ** * ** *** ## 3.7 (2025-01-20) bugfix Fixed an issue where **Template** creation could fail due to status casing inconsistencies. *** ** * ** *** ## 3.6 (2025-01-16) ![image-20250116-163559.png](https://booking.apwide.com/__attachments/a_069ce23138d5a9af8f08c6b7f78af230ee3ca09d84bd1ea38b474981cbf1cf6e/image-20250116-163559.png?cb=750cdc51383ad252425ba6a3e02fd898) Booking screen with suggestions and conflict detection improvement Added new screens for *creating* and *rescheduling* bookings, including available resource suggestions. improvement Implemented a **List View** to display all bookings in a **Booking** **Flow**, with filters for dates, requester, resources, and statuses. improvement Added a **Reschedule** button to the Booking activity tab. improvement Moved the **Rovo Banner** from the **Booking** **Flow** to the **Booking Hub**screen. --- language: "en" --- # Create a Booking Flow **Booking Flows** are configurations that allow you to book resources in Jira or Jira Service Management. Each Booking Flow consists of a resource pool and a booking configuration. You can create Booking Flows using the **guided setup wizard** for a faster, recommended configuration, or **manually create a custom** Booking Flow when you need full control over Jira elements, such as for team-managed spaces or advanced setups. *** ** * ** *** ## Requirements * You must be a **Jira Administrator** to create Booking Flows. For more details, refer to the [Permissions](https://booking.apwide.com/doc/permissions.md) article. *** ** * ** *** ## Create a Booking Flow In the [Booking Hub](https://booking.apwide.com/doc/booking-hub.md), click **+ Booking Flow** and follow the steps described below: **Important** The setup wizard is available only for **company-managed Jira spaces** . For team-managed spaces, create a Booking Flow manually using the **custom flow creation process** below. ### Step 1: What to book Select what type of resource you want users to book. Examples include: * **Car** * **Conference room** * **Consultant** * **Desk** * **Medical device** * **Mobile device** * **Parking slot** * **Software license** * **Support call** * **Other** **Info** If you select **Other**, enter a custom resource name. ### Step 2: Resource type Choose where your resources are managed: * **Apwide Booking:**Manage resources directly in the Booking app. * **Jira Assets (AQL):**Pull resources from a Jira Assets schema using an AQL query. This option is available only if Jira Assets is enabled on your instance. ### Step 3: Resource list Define or select the resources that can be booked. * Add new resources, or * Select existing resources from Apwide Booking or Jira Assets. Use **+ Add a resource** to expand the list. **Info** Assets filters and capacity attributes can be defined at the end of the creation process, when editing your booking flow. ### Step 4: Jira space Choose where booking requests will be created. * **Create a new Jira software space** * **Use an existing company-managed space** If you create a new space, it is created automatically during setup. ### Step 5: Experience Choose how users will book the selected resources. Available booking experiences include: * Time slots * Start and end time * Start time and duration * Start time, end time, and duration For details on each option, see the [Booking Experience](https://booking.apwide.com/doc/customize-the-booking-experience.md) documentation. ### Step 6: Summary 1. Review a complete overview of your selections, including: * Resource type and list * Jira space configuration * Booking experience * Jira elements that will be created or updated 2. Click **Start** to create the Booking Flow. A progress bar shows the creation status. Keep the page open until the process finishes. ### Step 7: Completed After the process completes, a confirmation message is displayed. You can then: * **Open** the Booking Flow, or * **Configure** it further using the editing screen. *** ** * ** *** ## Create a Custom Booking Flow Use a **Custom Booking Flow** to manually configure all booking settings. This method is required for **team-managed Jira spaces**. ### Step 1: Start the Custom Flow Creation 1. Go to the **Booking Hub**. 2. Click **+ Booking Flow**. 3. In the first wizard step (**What to Book**), locate the information box. 4. Click **Custom Flow Creation Process**. You are redirected to the Booking Flow configuration page. ### Step 2: Configure General Settings 1. In the **General** section, configure the following: * **Enabled:** Enable or disable the Booking Flow. * **Name:** Enter a name for the Booking Flow. * **Description:** Enter a short description. * **Space:** Select the team-managed Jira space for booking requests. * **Work Type:** Select the work item (issue) type used for bookings. ### Step 3: Select the Booking Experience 1. In the **Booking Experience** section, select how users will book resources: * Time Slots * Start Time and End Time * Start Time and Duration * Start Time, End Time, and Duration 2. Review the default settings. ### Step 4: Configure Custom Fields 1. In the **Custom Fields** section, select: * **Start Field:** A Date-Time Picker field for the booking start time. * **End Field:** A Date-Time Picker field for the booking end time. 2. Ensure both fields are available on the **Create** screen for the selected work type. ### Step 5: Configure Resources 1. In the **Resources** section, choose one option: * **Define and Manage Your Resources in Apwide Booking** * **Define and Manage Your Resources Using Jira Assets (AQL)** 2. If using Jira Assets: * Select the schema and object type. * Enter an AQL query. * Click **Test** to validate the query. 3. Configure the following: * **Resource Field:** Jira custom field used to store the selected resource. * **Resource Type:** Enter a descriptive name for the resource type (for example, Desk or Projector). ### Step 6: Configure Conflict Handling and Automation 1. (Optional) Enable one or both options: * **Link Conflicting Work Items:** Automatically link overlapping bookings. * **Auto Approve Request:** Automatically approve or reject requests based on conflicts. ### Step 7: Configure Statuses 1. In the **Statuses** section, select: * **Confirmed Statuses:** Statuses that represent valid bookings. * **Trigger Status:** Status that triggers conflict detection and automation. 2. Work items rescheduled from the Booking App also transition to the trigger status. ### Step 8: Save the Booking Flow 1. Review your configuration. 2. Click **Save**. The custom Booking Flow is created and ready to use. --- language: "en" --- # Create a JSM Request This article explains how to enable **Booking** on **Jira Service Management (JSM)**, create and configure a request type, adjust field settings, and understand current limitations. *** ** * ** *** ## Requirements To enable booking on JSM, you need: * [**Jira Service Management**](https://www.atlassian.com/software/jira/service-management)installed and active. * A configured **Booking Flow** in a Jira servicespace. * A workflow transition from the first status back to itself. This is included by default if you use the Booking Flow templates. **Info** When you create a **Booking Flow** in a *new* Jira space, a company-managed *software* project is automatically created. If you want to create a **Booking** **Flow** on a ***service project*** , you must first create the Jira space manually. Once created, you can select it when [creating a Booking Flow](https://booking.apwide.com/doc/creating-a-booking-flow.md). *** ** * ** *** ## Configure your JSM Request When you create a Booking Flow from a template in a Jira service space, a JSM request type is created automatically. To make it visible in the customer portal: 1. In your space, go to **Space settings \> Service requests** (or **Unassigned**, depending on your setup). 2. Locate the request. 3. Click the three dots (**...** ) next to the request and select **Edit portal groups**. 4. Assign the request to the desired portal groups. 5. Click **Save**. *** ** * ** *** ## Create a new JSM Request If the JSM request was not created automatically with your Booking Flow, complete these steps: 1. Open your **JSM** **Space Settings**. 2. Go to **Request management** \> **Request types**. 3. Click **Create request type** \> **Create blank**. 4. Enter a **Name** (for example, "Book a car"). 5. Select a **Portal group**. 6. Choose a **Work type** (for example, "Car Booking"). 7. Click **Add**. 8. Click **View in Portal** to verify your new request. *** ** * ** *** ## Examples ![image-20260112-100306.png](https://booking.apwide.com/__attachments/a_e7a35a1e67aacd69f88195f291c27722e6d9cce93b23dc28b40ad92818861fcd/image-20260112-100306.png?cb=f793985bf89a56035dcc32cbdd387ed0) Example of a JSM Request Configuration ![image-20260112-100426.png](https://booking.apwide.com/__attachments/a_1f7f1007ec8b63f79aa9ea29cb2ae3ca23e9480f4a0ecbfdda51db79247bdaed/image-20260112-100426.png?cb=2f7782a11076576fc7cd670b664435d7) Example of a JSM Request Creation ![image-20260112-100655.png](https://booking.apwide.com/__attachments/a_b51c7ae101015d4d25dcd7e9b5f1d1ec29acea9849b755f5aaeeaeb70b661be0/image-20260112-100655.png?cb=86fd002d9963b9e935152e08bcdc61df) Example of a JSM Request View ![image-20260521-111433.png](https://booking.apwide.com/__attachments/a_08740538ea602b921d7857966445f13a06aca5d982aa1adf7859640fde1116c6/image-20260521-111433.png?cb=44ccb418b012879a14299063f0c5ea8e) "Customer Portal" shortcut in your Booking Flow --- language: "en" --- # Customize the Booking Experience When configuring your **Booking Flow** , you can choose from three different **Booking Experiences**: * **Time selection**, where users select a start and end, or a duration, then see which resources are available for that time. * **Time slots**, where users choose a predefined time slot or a resource, then see the corresponding availability. * **Resource availability**, where users select a resource first, then check its availability in the calendar for the selected day. Each option has its own set of settings and particularities that affect how users can book a resource. The system accepts time and date values using: * `w` for weeks * `d` for days * `h` for hours * `m` for minutes *** ** * ** *** ## Time Selection Where users select a start and end, or a duration, then see which resources are available for that time. ![79287dbe-71a2-429c-9310-49987f664e4e.png](https://booking.apwide.com/__attachments/a_ea9eb78c6cad260c05f66eaed87295dbfc29acda22c14f6a120b3ed2543cfe54/79287dbe-71a2-429c-9310-49987f664e4e.png?cb=bb21bd2ea8c9c619fc281e0aa6daa7e0) Time Selection Booking Experience ### Steps 1. In the [Booking Hub](https://booking.apwide.com/doc/booking-hub.md), click the **Open** button next to the **Booking Flow** you want to edit. 2. Click **Edit Booking Flow**. 3. Go to the **Availability** tab. 4. Select **Time Selection** in the Booking Experience field 5. Select the fields you want to display in your booking field: 1. **Start + End** to display the Start and End fields 2. **Start + Duration** to display the Start and Duration fields 3. **Start + Duration or End** to display the Start, End and Duration fields 6. Define the **Default Start Time** . **Examples**: * `1d` → Tomorrow at 00:00 * `1d 8h` → Tomorrow at 08:00 * `8h` → 8 hours from now 7. Define the **Default Duration** . **Examples**: * `1h 15m` → 1 hour and 15 minutes * `48h` → 2 days * `1w 2d` → 1 week and 2 days 8. *(Optional)* Define the **Maximum Duration**. * This limits how long a resource can be booked. * **Example** : `8h` prevents bookings longer than 8 hours. 9. Customize the label for the **Duration** field. **Example** : Use *Durée* (French) or *Duración* (Spanish) instead of "Duration". *** ** * ** *** ## Time Slots Where users choose a predefined time slot or a resource, then see the corresponding availability. ![image-20260320-122849.png](https://booking.apwide.com/__attachments/a_8955028fe7e8f070aeaa9e2c39b28b5c04b8c64e0cfaec6298f81546eea5ecac/image-20260320-122849.png?cb=4b4a1e32adf0ae9f041337a0697e5c42) Time Slots Booking Experience This option allows you to define recurring availability windows. 1. In the [Booking Hub](https://booking.apwide.com/doc/booking-hub.md), click the **Open** button next to the **Booking Flow** you want to edit. 2. Click **Edit Booking Flow**. 3. Go to the **Availability** tab. 4. Select **Time Slots** as your **Booking Experience**. 5. Select the **Timezone**where the resource is located. 6. Choose the days of the week and a time range to define an **Availability Window**. 7. Define the **Duration(s)**of the booking slots. advanced edition Your users can choose the slot duration when adding multiple durations separated by commas, e.g. `1h, 2m, 3h` ![image-20260415-152337.png](https://booking.apwide.com/__attachments/a_742195803b5c999c67f3a6ecdb3b7f4beebc8ffcfb83b5a3965d8f8e57a6603b/image-20260415-152337.png?cb=eb6f75ddd135e7034dd0f3241c147ba8) Tip Click **+Add availability** to create multiple availability windows ### Additional Settings You can define the booking window using one of two methods under the **Additional settings**: * **Period of Rolling Time:** Define a rolling window of time for booking. * **Custom Date Range:** Define a specific start and end date when a user can book a resource. #### Period of Rolling Time 1. Under **Additional Settings** , select **Period of rolling time**. 2. Define the **Rolling time** using the accepted values. This sets the maximum time into the future a user can book a resource. **Examples:** * `d` means booking is possible until the end of the same day. * `1d` means booking is possible for the same day and the day after. * `0w` means booking is possible until the end of the current week. * `1w` means booking is possible until the end of the current week and the week after. 3. Define the **Minimum notice time** . This determines the minimum amount of time required before a user can make a booking. **Examples:** * `0d` means booking is possible from now on. * `8h` means booking is possible from 8 hours from now. * `1d 14h` means booking is possible from tomorrow at 14:00. * `0w` means booking is possible from now on. * `1w` means booking is possible from the beginning of next week. 4. Define the **Start time increment**. This setting defines the frequency of your booking start times, such as every 15, 30, or 60 minutes. #### Custom Date Range 1. Under **Additional Settings** , select **Custom Date Range**. 2. Define the **Start** and **End** **Dates**where a user can book a resource. 3. Define the **Minimum notice time** and **Start time increment** . These behave the same as for **Period of Rolling Time**. *** ** * ** *** ## Resource Availability Where users select a resource first, then check its availability in the calendar for the selected day. ![ff6c5aca-f555-42d1-8c28-09190b62b957.png](https://booking.apwide.com/__attachments/a_21906249d1b3adb3128f271dfeb6df233965f7065c1d802393e7c5e20811707f/ff6c5aca-f555-42d1-8c28-09190b62b957.png?cb=1566a68eddc366e7e7c8e40d396ec8df) Resource Availability Booking Experience ### Steps 1. In the [Booking Hub](https://booking.apwide.com/doc/booking-hub.md), click the **Open** button next to the **Booking Flow** you want to edit. 2. Click **Edit Booking Flow**. 3. Go to the **Availability** tab. 4. Select **Resource Availability** in the Booking Experience field 5. Select the fields you want to display in your booking field: 1. **Start + End** to display the Start and End fields 2. **Start + Duration** to display the Start and Duration fields 3. **Start + Duration or End** to display the Start, End and Duration fields 6. Define the **Default Start Time** . **Examples**: * `1d` → Tomorrow at 00:00 * `1d 8h` → Tomorrow at 08:00 * `8h` → 8 hours from now 7. Define the **Default Duration** . **Examples**: * `1h 15m` → 1 hour and 15 minutes * `48h` → 2 days * `1w 2d` → 1 week and 2 days 8. *(Optional)* Define the **Maximum Duration**. * This limits how long a resource can be booked. * **Example** : `8h` prevents bookings longer than 8 hours. 9. Customize the label for the **Duration** field. **Example** : Use *Durée* (French) or *Duración* (Spanish) instead of "Duration". --- language: "en" --- # Get Started With **Apwide Booking**, schedule assets with pre-built templates, flexible resource pools, and real-time conflict detection. Our App works with Jira issues, workflows, and custom fields to keep your bookings organized and conflict-free. *** ** * ** *** ## Requirements Before proceeding with the Booking App installation, ensure that you meet the following requirements: * A **Jira Cloud** site. If you don't have one, [create a new free Jira Cloud site](https://www.atlassian.com/try/cloud/signup?bundle=jira-software&edition=free). * **Jira Administrator** permission on your site. *** ** * ** *** ## Get Started ### Step 1: Install Apwide Booking Access the [Apwide Booking Listing](https://marketplace.atlassian.com/apps/1236123/booking-resource-reservation-for-jira-and-jsm) and install Apwide Booking for free. ### Step 2: Access the Booking App 1. In Jira, click **Apps** in the main navigation menu. 2. From the drop-down menu, select **Booking**. ### Step 3: Create your first Booking Flow 1. Click **+ Booking Flow** in the [Booking Hub](https://booking.apwide.com/doc/booking-hub.md). 2. Choose a **Template** that matches the type of resource you want to book. 3. Select a **Jira space**(new or existing). 4. Choose the **Resources**. 5. Click **Create**. For detailed instructions and advanced options, refer to the [Creating a Booking Flow](https://booking.apwide.com/doc/creating-a-booking-flow.md) article. ### Step 4: Book your first Asset 1. In the [Booking Hub](https://booking.apwide.com/doc/booking-hub.md), locate the **Booking Flow** you created in **Step 3**. 2. Click **Book** . ![image-20241212-191041.png](https://booking.apwide.com/__attachments/a_4862f1f52304d02cd8275c46dc927b5842dcb11e3cbb31cb218367400866872f/image-20241212-191041.png?cb=3aad5d5908c1013581df8b0255c4d735) Booking Flow with the Book button highlighted in red 3. In the **Book**dialog: 1. Select the **Start Date** and **End Date**of the reservation. 2. Choose the **Resource**you want to book. 3. Enter a **Summary** for your Booking. ![image-20250120-215121.png](/__attachments/a_c88be7a6b8fcbc191b29582fa7a2fc74fe5f4cf7427152c937d7e6cc87e90c8e/image-20250120-215121.png?cb=8f3b508dc745a2938b38d3102e54ae44) 4. Click **Book** and boom---your first asset is officially booked with the **Apwide Booking** App 🚀 *** ** * ** *** ## Related Articles * [Booking Hub](https://booking.apwide.com/doc/booking-hub.md): The Booking Hub gives you an overview of all your Booking Flows. * [Booking Flow](https://booking.apwide.com/doc/booking-flow.md): Each Booking Flow has a resource pool and a booking configuration. * [Permissions](https://booking.apwide.com/doc/permissions.md): How permissions work in Apwide Booking. --- language: "en" --- # Book a Resource In this article, you'll learn how to book a resource in Apwide Booking using different methods: * From the **Booking Hub**. * From a specific **Booking Flow**. * From a **Timeline**. * Using Jira **Create**button. * Using **Book with Rovo**. *** ** * ** *** ## Book a Resource ### From the Booking Hub 1. Access the [Booking Hub](https://booking.apwide.com/doc/booking-hub.md). 2. Locate the **Booking Flow**for the desired resource. 3. Click **Book**. 4. In the dialog: * Set the **Start Date** and **Time**. * Set the **Duration** or the **End Date** and **Time**. * Select resource to book. * Enter a descriptive **Summary**for the booking or keep the default text. 5. Click **Book**. ### From a Booking Flow 1. In the [Booking Hub](https://booking.apwide.com/doc/booking-hub.md), locate the desired **Booking Flow**. 2. Click **Open**. 3. Click **+Book**. 4. In the dialog that opens: * Set the **Start Date** and **Time**. * Set the **Duration** or the **End Date** and **Time**. * Select resource to book. * Enter a descriptive **Summary**for the booking or keep the default text. 5. Click **Book**. Watch the video below for a step-by-step demonstration on how to book a resource [Booking App UC-1.mp4](https://booking.apwide.com/__attachments/a_a3710216213cec8c5df85c72219390015484fb9ef3095816bc6e57a491f31544/Booking%2520App%2520UC-1.mp4.md?cb=3c218f94d133a36675f3745114b9e8c4) ### From a Timeline 1. In the [Booking Hub](https://booking.apwide.com/doc/booking-hub.md), locate the desired **Booking Flow**. 2. Click **Open**. 3. Go to the **Timeline** tab. 4. On the **Timeline**, click the exact date, time, and swimlane that corresponds to the resource you want to book. 5. Verify that the automatically populated **Start Date** and **Resource** match your selection, and adjust the **Duration** or the **End Date** and **Time**if needed. 6. Click **Book**. 7. The reservation will appear on the **Timeline**. ### Using Jira Create button 1. Click the **Create** button in Jira. 2. Select a **Space** and **Issue Type** linked to a Booking Flow. 3. Set the **Start Date Time**. 4. Set the **Duration** or the **End Date Time**. 5. Select an available **Resource** from the suggested list. Only resources available at the selected time will appear. 6. Complete the **Summary** field if needed. 7. Click **Create** to finalize the booking. **Info** Suggestions are powered by smart availability logic and conflict detection. Ensure that the Booking Flow is properly configured. ### Book with Rovo When Rovo is enabled on your Jira instance, you can use the **Booking Clerk** (Rovo Agent) to create a booking using natural language: 1. From the **Booking Hub** or a **Booking Flow** , click **Book with Rovo**. 2. In the chat dialog, describe your booking request. 3. Follow the prompts to confirm the booking. --- language: "en" --- # View Your Booked Resources In this article, you'll learn how to view your booked resources: 1. **In Booking**, with the List and Timeline 2. **In Jira**, with Filters and Dashboards 3. **In Time Squad**, timelines for advanced use cases *** ** * ** *** ## In Booking 1. Access the [Booking Hub](https://booking.apwide.com/doc/booking-hub.md). 2. Locate the **Booking Flow** for the desired resource. 3. Click **Open**. ### List Tab Go to the **List**tab to view all booked resources. **Tip** You can filter the results by: * **Start Date** and **End Date** * **Reporter** * **Resources** * **Statuses** ![image-20250227-132159.png](https://booking.apwide.com/__attachments/a_1e1c1dbdb5dd791a566cd37e955ac1914f90a0309cb4abebe1fa1f28a8f243de/image-20250227-132159.png?cb=d433fc5b432baa58cb6d81ea9cba5f50) Booking requests part of a Booking Flow - List View ### Timeline Tab In the **Booking Flow** , click the **Timeline**tab to see all resource reservations displayed on a timeline. **Tip** Use the controls at the top right to: * **Move to today's date** * **Navigate** through the timeline (or drag the timeline) * **Zoom In** or **Zoom Out** (or mouse scroll on the timeline) ![Booking Timeline (1).gif](https://booking.apwide.com/__attachments/a_78ea0c8500e66889669fdd574d7d12c787c579d77353cbcc5f64e3bcc5bdda03/Booking%20Timeline%20(1).gif?cb=fc54fc7116b02f695e04a95cf596b78e) Booking requests part of a Booking Flow - Timeline View *** ** * ** *** ## In Jira Because booking requests are standard Jira work items, you can use Jira filters, dashboards, gadgets, and reporting features to search, organize, and visualize your bookings. *** ** * ** *** ## In Time Squad If you use Assets to store your resources, you can add an additional Assets field to your booking requests to link them with Assets objects (refer to the [Sync Booking and Assets fields](https://booking.apwide.com/doc/sync-booking-and-assets-fields.md) documentation). You can then use [Time Squad](https://marketplace.atlassian.com/apps/1223588/time-squad-roadmap-and-timeline-for-jira?hosting=cloud&tab=overview) - another app from Apwide available on the Atlassian Marketplace - to display your resources and bookings on advanced timelines and create dedicated views for different stakeholders. --- language: "en" --- # Jira Automation Jira Automation can be combined with the Booking App to extend booking capabilities and automate workflows. *** ** * ** *** ## How Jira Automation Works Jira Automation rules respond to events such as work item updates or transitions. When a rule is triggered, it can perform actions related to bookings, such as: * Creating bookings * Updating existing bookings * Synchronizing booking data with other Jira components These actions use dedicated Booking App automation components. *** ** * ** *** ## When to Use Jira Automation Use Jira Automation when you need to: * Display booking information in Jira Assets * Automatically create related bookings (for example, equipment after a room is booked) * Manage shared resources across multiple booking flows * Automate repetitive booking tasks *** ** * ** *** ## Next Steps Use the following articles to configure specific automation use cases: * [Action: Create Apwide Booking](https://booking.apwide.com/doc/action-create-apwide-booking.md) * [Action: Edit Apwide Booking](https://booking.apwide.com/doc/action-edit-apwide-booking.md) * [Sync Booking and Assets fields](https://booking.apwide.com/doc/sync-booking-and-assets-fields.md) * [Block a resource for the whole day](https://booking.apwide.com/doc/block-a-resource-for-the-whole-day.md) * [Book parking spots for appointments](https://booking.apwide.com/doc/book-parking-spots-for-appointments.md) --- language: "en" --- # 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](https://booking.apwide.com/doc/permissions.md) article. *** ** * ** *** ## Edit a Booking Flow 1. In the [Booking Hub](https://booking.apwide.com/doc/booking-hub.md), 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: #### 1: Define and Manage Resources in Apwide Booking 1. In the **Resources** tab, select **Define and manage your resources in Apwide Booking**. 2. Click Edit list to add new resources. 3. Enter the **Resource type**. #### 2: Define Manage Resources using Jira Assets (AQL) Connect to a Jira Assets schema and pull in objects using an AQL (Assets Query Language) filter. **Important** This option is only available when Jira Assets is enabled on the Jira instance. 1. In the **Resources** tab, select **Define and manage your resources using Jira Assets (AQL)**. 2. Enter the **Resource type**. 3. Select the **Jira Assets** schema where your resources are stored. The system generates a default **AQL query** based on your schema and object type. You can customize this query to apply filters when needed. 4. Use the **Test**button to verify that the query returns the expected resources. 5. (optional) Choose Select attributes to be displayed as resource filters. 6. (optional) advanced edition Choose Integer attribute to be used as capacity. 7. Click **Save**. 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 your booking history. If you need to switch, we suggest creating a new **Booking Flow**instead. ### Workflow Tab * **Confirmed Statuses**: Define the statuses that represent valid bookings. Only bookings with these statuses will be included in the conflict-checking process. #### Link conflicts 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](https://booking.apwide.com/__attachments/a_b5d12e9a549ebc992d12216886103f840a2224ce38f6665378a5b0aeb8ffdb02/image-20250414-165631.png?cb=63562436852d34eb919088dac9c49e4e) Workflow example ### Availability Tab For details on configuring the **Availability** tab, refer to the [Customize the Booking Experience](https://booking.apwide.com/doc/customize-the-booking-experience.md) 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](https://booking.apwide.com/doc/permissions.md) documentation. --- language: "en" --- # Permissions ## Default behavior * All Jira users have access to the [Booking Hub](https://booking.apwide.com/doc/booking-hub.md) and all active [Booking Flows](https://booking.apwide.com/doc/booking-flow.md) * Only Jira Administrators can create and configure them This ensures that Booking Flows remain aligned with Jira configuration (issue types, workflows, fields). The Jira space permissions will always apply when users will create booking requests from the Booking Flows, using the **+Book** button. *** ** * ** *** ## Jira Administrator The **Jira Administrator** permission is required in order to perform the following operations: * Create a new Booking Flow * Edit the Booking Flow configuration **Grant Jira Administrator permissions** To grant Jira Administrator permission to a user, refer to the following article: [Give users admin permissions](https://support.atlassian.com/user-management/docs/give-users-admin-permissions/) *** ** * ** *** ## Booking Flow Permissions 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. 1. Open a Booking Flow 2. Click Edit Booking Flow 3. Go to the **Permissions** tab *(Jira Admin only)* 4. Add users or groups who can edit the flow Users with this permission can edit the Booking Flow configuration, and the creation of new Booking Flows remains restricted to Jira Administrators. --- language: "en" --- # Rovo Agent Apwide Booking provides the **Booking Clerk**, a dedicated Rovo Agent, to simplify resource bookings using natural language. You can start the Booking Clerk directly from Apwide Booking or from Jira. Once you've completed the [++Booking Flow++](https://booking.apwide.com/doc/booking-flow.md) configuration, you can ask the **Booking Clerk** to book a resource for you. **Example requests:** * "Can you book a parking slot for me tomorrow morning?" * "I need a desk next Wednesday from 2PM to 4PM." * "What cars are available tomorrow between 8AM and 5PM?" The Booking Clerk guides you through the booking and creates the request when all required information is provided. **Important** The **Booking Clerk** can create booking requests but cannot reschedule existing bookings. [Booking App UC-2.mp4](https://booking.apwide.com/__attachments/a_43f56f7d761ecca2185ca2a9f30fdcef4aafa518ca7eaf3c3cd202797a1666c5/Booking%2520App%2520UC-2.mp4.md?cb=07c46b239ff4b348dc39d064230f89fc) Video Example: Booking a vehicle with the Booking Clerk *** ** * ** *** ## Start the Booking Clerk You can start the Booking Clerk directly from Apwide Booking. ### From the Booking Hub 1. Open the **Booking Hub**. 2. Click **Book with Rovo** at the bottom of the page. ### From a Booking Flow 1. Open a **Booking Flow**. 2. Click **Book with Rovo** in the header. This opens the Booking Clerk and lets you create a booking using natural language. **Info** If Rovo is not enabled, the **Book with Rovo** button remains visible but has no effect when clicked. *** ** * ** *** ## Open the Booking Clerk from Jira You can also access the Booking Clerk directly from Jira. This method is useful if you are not currently in Apwide Booking. 1. In Jira, click **Ask Rovo** at the top. 2. Click **Rovo** to switch to another agent. 3. Type **Booking** to search for agents. 4. Select **Booking Clerk**. ![image-20251223-143730.png](https://booking.apwide.com/__attachments/a_f5f178d52f319c3736189b803b83617f705d5cf697247bdfb4aee9b90cf25032/image-20251223-143730.png?cb=e1550f1f656f8ba6f8033b4654792542) Open Ask Rovo and select Booking Clerk from the agent list. --- language: "en" --- # Rovo Skills Rovo Skills allow you to reuse Booking App capabilities inside custom Rovo Agents created with Atlassian Studio. This article explains what Rovo Skills are, how they work, and what each available skill does. *** ** * ** *** ## What Are Rovo Skills? Rovo Skills are reusable actions that extend the capabilities of a Rovo Agent. The Booking App provides predefined skills that can be added to custom Rovo Agents. These skills allow agents to interact with booking data and perform booking-related operations. *** ** * ** *** ## How Rovo Skills Work Rovo Skills are added to a custom Rovo Agent from Atlassian Studio. To use them: 1. Open your custom Rovo Agent in Atlassian Studio. 2. Go to the scenario configuration (for example, the default scenario). 3. Select skills from the skills library. 4. Add the required Booking App skills to the agent. ![image-20260319-121901.png](https://booking.apwide.com/__attachments/a_a46931e93ec23b803c55ed0e4fe18244a00a4811d820bbb8b215f71b6908c083/image-20260319-121901.png?cb=66be92e7705a8551900de5d870d1777e) Selecting Rovo Skills in Atlassian Studio Once added, the agent can use these skills when interacting with users. For example, a Rovo Agent used in a Jira Service Management portal can create booking requests or suggest available resources based on user input. *** ** * ** *** ## Available Booking App Rovo Skills The Booking App provides the following skills: ### Create booking request Creates a Jira work item to request a booking for a resource. Use this skill when you want users to submit booking requests directly through a Rovo Agent, such as from a Jira Service Management portal. #### Find available resources Returns a list of resources available for booking based on given criteria. Use this skill to help users identify available resources before creating a booking request. #### Get booking flows Returns the booking flows defined in the Booking App. Each booking flow represents a type of resource or booking process. Use this skill when the agent needs to understand or present available booking options. *** ** * ** *** ## When to Use Rovo Skills Use Rovo Skills when you need more flexibility than the [Booking Clerk](https://booking.apwide.com/doc/rovo-agent.md). The Booking Clerk already uses the same underlying skills, but Rovo Skills allow you to customize how those capabilities are exposed and used. Use Rovo Skills when you need to: * Customize the agent behavior, such as language, tone and voice, interaction style * Adapt the booking experience to specific use cases or audiences * Make the agent available in environments where the Booking Clerk is not supported, such as the Jira Service Management portal * Reuse Booking App capabilities in custom Rovo Agents --- language: "en" --- # Sync Booking and Assets fields You may want to see the linked booking requests while browsing your Assets. ![image-20260319-104432.png](https://booking.apwide.com/__attachments/a_616ae2bdddaade9b375c96e4d48642be9a8db9c23fdea55d3218aa7aae2b32a2/image-20260319-104432.png?cb=cb19690317d12931b81227ed30423731) Show the bookings in your Jira Assets *** ** * ** *** ## Requirements * Booking Flow configured with **Jira Assets resources**. * Access to **Jira Automation**. * Familiarity with creating **automation rules** and using **smart values**. * **Jira Administrator** permission if you must create a new Assets field (step 1). *** ** * ** *** ## Step 1: Assets object field If not already there, create a new Jira custom field with the type "Assets objects", and make sure it is available in context of your booking request (in can be visible or hidden from your screens). ![image-20260319-102258.png](https://booking.apwide.com/__attachments/a_5070a8f3729342fc2c4e47f9e896205a7977d901b8e67e555b7203aaf65d2130/image-20260319-102258.png?cb=eb6a6311b9122233e718c3483ec0523b) In the field configuration of this field, make sure you show the same Assets than the ones used in your Booking Flow. ![image-20260319-102413.png](https://booking.apwide.com/__attachments/a_6be47d87117a8b958a655e7c70fc28a6d6ccb50086a545092b5baf5a5d73766f/image-20260319-102413.png?cb=e3e941eaeb8ee2ac0702749f0799af29) *** ** * ** *** ## Step 2: Jira Automation Configuration Create a new **Jira Automation** **rule** with the following configuration: ![image-20260319-103156.png](https://booking.apwide.com/__attachments/a_d0ef1c0ec39e652b74bc22cba74612271225ae53be391dc7f1316469bbc8c4fd/image-20260319-103156.png?cb=b87373ee8ca727a4126d99943ea509fa) Jira Automation Configuration ### Trigger: Field value changed The rule will be triggered when the Booking field is created or updated. ![image-20260319-103233.png](https://booking.apwide.com/__attachments/a_fe90743b0cc736f18d0562a5c645e8679572c6732d457563acf05df4c96bcd03/image-20260319-103233.png?cb=a0722a62c84d502ea021ddb4faa6596c) You can add a condition to only trigger the rule for the project and work type used by your Booking Flow. ### Action: Create variable Extract the Asset ID from the Booking field. ![image-20260319-103740.png](https://booking.apwide.com/__attachments/a_38422841540980e135291ecb709475154b911bcfa43b4446dc4de6bfebb6c01c/image-20260319-103740.png?cb=cf1efa1f7b6c0855d5532ec9ff798832) **Variable name:** assetId **Smart value:** {{issue.customfield_XXXXX.id.split(":").get(1)}} You can find the custom field ID when clicking on the smart value icon and searching for "Booking". ### Action: Edit work item Update your Assets field with the correct Asset. ![image-20260319-103315.png](https://booking.apwide.com/__attachments/a_238d74add85681d28910cac5c3b3a19711af06bc3677da857ce58e1b079d63ad/image-20260319-103315.png?cb=f42ab509db3a80bfb22c3a0dfa2c309b) **Asset field name:** objectId = {{assetId}} *** ** * ** *** ## Need Assistance? For support with Jira Automation with Booking, reach out to our [++Customer Portal++](https://apwide.atlassian.net/servicedesk/customer/portal/1/group/1/create/1). --- language: "en" --- # Troubleshooting Below, you'll find some common issues encountered by our customers and how to solve them. ## 1. The Booking field does not display correctly during a Reschedule transition ![image-20260316-111957.png](https://booking.apwide.com/__attachments/a_bc11569cbe3b8b8bfdd46d02106512b964f3a3bc86ebeccd366e8b25d5b30cec/image-20260316-111957.png?cb=39d8c4bdeffde44da78043242dfd7b54) Booking field does not display correctly This issue occurs because Forge custom fields are not rendered correctly in Jira's legacy transition experience. Atlassian introduced a [new transition experience](https://community.atlassian.com/forums/Jira-articles/Now-GA-try-the-new-issue-transition-experience-in-Jira/ba-p/2734436) in October 2024, but the rollout has been gradual and does not appear to be complete for all Jira sites. The new experience could initially be enabled from the Jira Labs section in each user's personal settings. However, Atlassian recently removed this option. ![image-20260721-074802.png](https://booking.apwide.com/__attachments/a_6544c901f64c4e04b41121e4217050d864df566c55f3c5967e0261bd33e8b08f/image-20260721-074802.png?cb=e806f649b19605f93bf81e3e21b8d53f) ![image-20260316-112416.png](https://booking.apwide.com/__attachments/a_8f24175f8512435225d4566f4f166beaeb7ce92d408438206a78f6b1d2f2bea6/image-20260316-112416.png?cb=9a54136f19e0ef7ea45fd6566bb97aad) Jira labs features We therefore recommend [contacting Atlassian Support](https://support.atlassian.com/contact/) and requesting that the new transition experience be enabled for your Jira site. Once enabled, Booking fields, along with other Forge custom fields, should display correctly on transition screens.