Versions Compared

Old Version 10

changes.mady.by.user Ryan Northfield (Deactivated)

Saved on

compared with

New Version Current

changes.mady.by.user Vincent Mutambuki

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Expand
titleWhat is Checkout?

Checkout is as an innovative solution designed to enhance IT Service Management (ITSM) and Enterprise Service Management (ESM) within the Jira Service Management (JSM) and Jira Assets framework. It aims to revolutionize the asset procurement process, covering the entire lifecycle from the initial request to the final retirement of assets. Checkout facilitates a highly collaborative environment, integrating various teams within an organization—such as internal customers, procurement, accounting, and external vendors—thereby streamlining operations and improving efficiency in procurement and asset management

Expand
titleCan I use Checkout in an existing Jira Service Management project?

Absolutely! As a project admin, navigate to Project settings > Checkout and turn on Checkout.

Expand
titleCan 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.

Expand
title 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.

Expand
titleWe 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?

...

We

...

have developed three distinct workflows tailored to different needs concerning Purchase Orders:

  1. Multiple Issues Order Flow:

...

  1. This flow allows you to interact with external vendors by providing them access to a purchase order from Jira Service Management. Vendors can log in to the portal and view the purchase order, as well as send related invoices. For each unique vendor item requested, Checkout will produce a linked issue along with a purchase order. This method ensures that 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.

  2. Single Issue Order Flow: This is the traditional method

...

  1. best suited for situations where vendors won't be logging into the portal to view their Purchase Orders or produce invoices.

  2. Disabled Purchase Orders: Ideal for those who have an alternate PO system

...

  1. in place, this option allows you to use Checkout mainly

...

  1. for facilitating organizational orders without generating a Purchase Order.

These workflows provide flexibility and cater to various scenarios based on your specific requirements regarding Purchase Orders.

You can configure your Checkout workflow setting here.

Expand
titleDoes Checkout integrate

...

with Jira Assets?

...

Yes, Checkout integrates with Jira Assets. It is supported in both the Datacenter and for cloud instances that are on Premium and Enterprise Edition of Jira Service Management.

Expand
titleCan I use Checkout as standalone asset management tool?

Absolutely. Checkout has a built in Asset management to allow customers on Jira Service Management standard and Server Edition to store their procured Assets. For premium customers, Jira Assets is available as an integration.

Expand
titleCan 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.

Expand
titleCan I create reports in Checkout?

Yes. Checkout offers the capability to generate two types of customizable reports. Asset reports and Order history reports.

Write into our Support Desk with any questions you have.