Versions Compared

Old Version 3

changes.mady.by.user Vincent Mutambuki

Saved on

compared with

New Version 4

changes.mady.by.user Vincent Mutambuki

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Expand
titleCan I user Checkout in an existing Jira Service Management project?

Absolutely!

Expand
titleCan I move Checkout issues and data to another project?

The simplest answers 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 cause of action is to move other issues and request types into Checkout project and rename the project. However, you should not rename 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?

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

  1. 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.

  2. 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.

  3. 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.