Skip to main content
Skip table of contents

Trigger Actions with Jira Workflows

image-20250306-114951.png

check-unselected.png Dt lite

check-selected.png Enterprise

Prerequisite

  1. Enable the integration from the Jira Integrations page.

  2. Enable the workflow as required.

Create an Issue on Jira upon satisfying a trigger condition

This workflow allows you to create a ticket on Jira of type “issue” upon satisfying the trigger conditions set on Dropthought. It helps you address issues promptly and convert unhappy customers to satisfied ones.

Follow the below steps to set up the workflow:

  1. Create a new trigger or edit an existing one.

  2. After specifying the trigger conditions, click the Add action button.

  3. Select Set up Workflows on Jira from the Select Action(s) screen.

                                                         

  1. Then click on Create an issue on Jira.

  2. Enter details like the Project name, Summary, Issue Priority, Labels, Assignee ID necessary to create a ticket on Jira.
    (Refer to the section on locating project name and assignee ID on Jira below this section for more details)

  3. Click on Apply and Save.

  4. The action card will be created. You can edit and delete anytime in the future.

  5. To activate the trigger, ensure that your trigger status is turned ON by clicking on the toggle at the top-right corner.

    image-20250326-045059.png

Locate Project Name & Assignee ID on Jira

  1. Project Name: You can find all jira projects from the left navigation panel within Jira.

  2. Assignee ID: From Jira,

    1. Hover over an assignee name.

    2. Click on View Profile and their profile will be open as a new tab.

      Screenshot 2025-03-26 103308.png
    3. Copy the assignee ID from the end of the URL. It will be an alphanumeric value.

      Screenshot 2025-03-26 103809.png
    4. Paste the assignee ID against the relevant field.


feedback-img.png
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.