Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

We've given a significant facelift to our Checkout catalog. Checkout does not need to be isolated in its own project. Instead, it can now be featured as a request type across any Jira Service Management catalog. This upgrade gives you the ability to have Checkout requests right where you need them, streamlining your service management process. For existing users, you can turn on this feature on at any time when you are ready. This feature is now default for new customers.

Hide Shipping Address and Procurement Department

We have introduced the ability for Checkout Project Admins to hide the Shipping Address and Procurement Department fields from the Portal.

We understand that these fields may not be relevant or useful for customers, so we want to give you the flexibility to hide them just like any other field in the Service Management Portal.

When setting up Checkout, admins can choose to hide these fields and designate a default value for the Ordering Department and Shipping Address. These default values will be automatically set when an order is created.

You have full control over enabling or disabling these fields in the admin section.

Checkout without creating purchase orders

We have added a new option that allows you to use Checkout without creating purchase orders.

In addition to the current two modes for creating purchase orders, we have introduced a third option. With this option selected, the creation of purchase orders will be disabled completely.

In this mode, users can use Checkout to display items on the portal, make requests and JSM agents fulfill them all without creating purchase orders.

When this mode is selected, the "Submit Order" button will be hidden from the Agent Order Details, disabling the creation of purchase orders.

Declining an item comment

Declined item comments will now be logged as a normal comment and the customer will be able to see the reason why the request was declined.

Powered by Released

  • No labels