Automatically Create Jira Issues for New Tickets

This document explains how to set up an automated workflow to create Jira issues for new tickets based on specified criteria.

Use Case

For example, you may want to create a Jira issue for any new ticket with potential savings of $500 or more in OneLens. This workflow will automatically create a Jira issue for tickets that meet this threshold.

Prerequisite

Before setting up this workflow, ensure that your Jira instance is integrated with OneLens. For integration details, click here.

Video Guide

For a more detailed walkthrough, refer to the video guide available here.

Step-by-Step Guide

1. Access the Workflows

1. Navigate to the workflow section of OneLens.

2. Click the Create button in the top-left corner to start a new workflow.

2. Create a New Workflow

1. A dialog box will appear asking for a workflow name. Enter a descriptive name (e.g., "Create Jira Issue for High-Value Tickets").

2. You can also add a description, which is optional.

3. Once you’ve filled in the details, click Create to proceed.

3. Choose the Trigger

1. In the workflow setup, select the Tickets option as your trigger.

2. You will then be prompted to choose between two options:

   1. Ticket is Created

   2. Ticket is Updated

3. For this scenario, choose Ticket is Created, as you want to trigger the workflow when a new ticket is generated.

Trigger Start

• You’ll have two options for how these conditions should be applied:

  • Trigger when all conditions match – the workflow will only trigger if all conditions are met.

  • Trigger when any condition matches – the workflow will trigger if any one of the conditions is met.

• You can configure multiple conditions by clicking on the Add Rule button.

Condition Configuration

Each condition involves filling out three fields:

1. Criteria: Choose the specific property of the ticket you want to filter by. You can use the following attributes:

   1. Ticket: Status, Category

   2. Recommendation: Potential Savings, Effort

   3. Resource: Name, Account, Region, Service, Tags

   4. Cost Center (Org Hierarchy): Cost Center, Category

   5. Policy: Name, Category

2. Limit: Set a comparison operator or criteria type for the selected attribute. The available options vary based on the chosen criteria.

3. Borderline: Set the specific value or list of values to compare against.

Example 1: Recommendation > Potential Savings

• Criteria: Potential Savings

• Limit: Greater Than

• Borderline: 500 (this would filter for tickets where potential savings are greater than $500).

You can set multiple conditions, each with unique criteria, limits, and boundaries, depending on the ticket types you wish to target.

Once all conditions are defined, click Save Changes to finalize the trigger.

4. Create the Jira Issue

• After setting the trigger and conditions, click Add Step.

• Select Jira from the left menu and then choose Create a Jira Issue.

Configuring the Jira Issue

You will now need to add the following details:

• Connection Type: Choose the appropriate connection type for your Jira instance.

• Project Name: Select the project to which the issue will be assigned.

• Epic: Specify the epic under which the issue will be categorized.

• Assignee: Choose the team or individual who will be responsible for the issue.

After entering the details, click Save Changes.

5. Publish Workflow

Review the workflow representation to ensure everything is set up correctly.

Click Publish to make the workflow active.

Result

Here is how your Jira issue will look like: