This article explains how to set up Raley Bookman app on your Atlassian instance.
Pre-requirements
- Jira cloud (any edition)
- Jira Service Management cloud (any edition)
- Jira admin access
Jira configuration
Your Jira instance will be used as Asset management system that keeps track of your bookable assets. In other words, a single issue (work-item) in Jira will be used to represent a particular single Asset that will be exposed for bookings via JSM Portal.
An example of such asset might be:
- Meeting room
- Corporate vehicle
- A person
You define your assets in Jira in one or several projects. Projects can be Company or Team-managed. You can define any workflow or issue type for your assets that make sense for your organization.
JSM Configuration
Your JSM Portal will be used as a front-door where customers or employees can make bookings for assets. As Jira admin, define one or several request types that correspond to the type of assets that you want to be bookable via portal.
An example of such Request type configuration is below:
Here we have 3 request types for different type of assets that we'll expose for bookings. Now, let's go to Bookman configuration console (Apps → Raley Bookman) and add the corresponding mappings like shown on the screenshot below:
In this example, we use one Service desk called Booking for Assets and map the JSM request type to a JQL statement which defines Asset issues bookable through that request type.
For instance, if user wants to book a Meeting Room then the Bookman will show all Jira Assets defined in project MTR.
There's no additional requirements towards your Booking Request types - they can contain any fields that you may find useful in your organization. Also, you have complete freedom in workflow configuration for your Booking project in JSM.
