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

« Previous Version 4 Next »

Create Jira Issue

Purpose: Allows the user to create an issue of a specified issue type in a specified project.

Available for Triggers:

  • Order Triggers

  • Vendor Triggers

  • Asset Triggers

Administrator must specify a Summary along with any other custom fields which are required for the issue type in the project they are creating.

The create issue action also comes with the Add additional metadata checkbox. This feature will be used to surface Checkout information on linked tickets, but the components to show the information are still under development.

Edit request Issue

Purpose: The Edit request issue action allows users to modify fields on the request action.

Available for Trigger Types:

  • Order Triggers

Send Webhook

Purpose: Allows the user to send a Webhook to a location. The administrators will need to define the following:

  • HTTP method

  • Webhook URL

  • Headers

If the HTTP method is POST or PUT, the body will be a JSON containing the Checkout Order information.

Available for Triggers:

  • Order Triggers

  • Vendor Triggers

  • Asset Triggers

Send Slack Message

The administrators will need to provide the following:

  • Webhook URL

  • Message

  • Channel or User

Available for Triggers:

  • Order Triggers

  • Vendor Triggers

  • Asset Triggers

Transition Issue

Allows the user to transition the issue to different statuses.

Available for Triggers:

  • Order Triggers

Edit asset attributes

Purpose

Available for Triggers:

  • Asset Triggers

Create request comment

Purpose

Available for Triggers:

  • Order Triggers

Decline order items

Purpose

Available for triggers:

  • Order Triggers

Disable submit order button

Purpose:

Available for Triggers:

  • Order Triggers

Enable Submit Order Button

Purpose:

Available for Triggers:

  • Order Triggers

  • No labels