FAQ

Can I use Checkout in an existing Jira Service Management project?

Absolutely!

Can I move Checkout issues and data to another project?

The simple answer is no. The assets and items associated with each other will be broken.

I used Checkout in its standalone format. Can I now integrate it with other projects by moving my request types and issues?

The best course of action is to move other issues and request types into the Checkout project and then rename the project. However, it's important not to change the project key.

We generally don't use Purchase Order, but we love that we can request items from a pictorial catalog. Can we turn off Purchase order generation?

Absolutely! We've developed three distinct workflows tailored to different needs concerning Purchase Orders:

Multi-issue Flow: For every unique vendor item requested, Checkout will produce a linked issue along with a purchase order. This method ensures each vendor views their respective purchase order when accessing the digital order via the portal. Additionally, vendors can generate invoices corresponding to these purchase orders.
Single-issue Flow: This is the traditional method, best suited for situations where vendors won't be logging into the portal to view their Purchase Orders or produce invoices.
No Purchase Order: Ideal for those who have an alternate PO system. This option allows you to use Checkout mainly to facilitate organizational orders without generating a Purchase Order.

Does Checkout integrate its Asset management with Jira Assets?

Partially. In the Data Center version, assets received through the Checkout procurement process can be copied via Checkout automation. However, this feature is not yet supported in the Cloud version.

Can I use Checkout as standalone asset management tool?

Absolutely.

Can I import existing assets into Checkout?

Absolutely! Our CSV importer is fantastic. You can map columns to fields including users and within minutes you are good to go.