Varolio Docs
  • 👋Welcome to Varolio
  • Overview
    • 💡How Does It Work
    • ✨Our Features
  • Automations
    • Automations Overview
    • Creating an Automation
    • Configuring Nodes
  • Plugins
    • OpenAI
      • Authentication
      • Models
    • Monday.com
      • Authentication
      • Functions
    • Slack
      • Authentication
      • Functions
    • Google Sheets
      • Authentication
      • Functions
    • Gmail
      • Authentication
      • Functions
    • Jira
      • Authentication
      • Functions
    • SendGrid
      • Authentication
      • Functions
    • Twilio
      • Authentication
      • Functions
    • Firebase
    • Notion
      • Authentication
      • Functions
    • Google Calendar
    • Google Drive
      • Authentication Guide
  • System Nodes
    • Cron
    • Javascript
    • Control Flow
Powered by GitBook
On this page
  • 1. Trigger - New Issue
  • 2. Trigger - Updated Issue
  • 3. Action (Create) - Create Issue
  • 4. Action (Create) - Update Issue
  • 5. Action (Search) - Search Issues
  • 6. Action (Create) - Link Issues
  • 7. Action (Search) - Get Issue
  1. Plugins
  2. Jira

Functions

The Jira Plugin enables the listed actions and triggers

1. Trigger - New Issue

Trigger an automation when a new issue is created in a specified Jira project.

  • Display Name: The name you want to set for the node.

  • Project ID: The key of the Jira project to monitor for new issues.

2. Trigger - Updated Issue

Trigger an automation when an existing issue is updated in a specified Jira project.

  • Display Name: The name you want to set for the node.

  • Project ID: The key of the Jira project to monitor for updated issues.

3. Action (Create) - Create Issue

Create a new issue in a specified Jira project.

  • Display Name: The name you want to set for the node.

  • Project ID: The key of the Jira project to create the issue in.

  • Issue type: The type of issue to create (e.g., Task, Bug, Story).

  • Summary: A brief summary of the issue.

  • Description (optional): A detailed description of the issue.

  • Assignee (optional): The username or email address of the person to assign the issue to.

  • Priority (optional): The priority level of the issue (e.g., Low, Medium, High).

4. Action (Create) - Update Issue

Update an existing issue in a specified Jira project.

  • Display Name: The name you want to set for the node.

  • Issue ID: The key of the issue to update.

  • Summary (optional): A new brief summary of the issue.

  • Description (optional): A new detailed description of the issue.

  • Assignee (optional): A new assignee for the issue.

  • Priority (optional): A new priority level for the issue.

  • Status (optional): A new status for the issue (e.g., In Progress, Done).

5. Action (Search) - Search Issues

Search for issues in a specified Jira project based on certain criteria.

  • Display Name: The name you want to set for the node.

  • Project key: The key of the Jira project to search for issues in.

  • Query (optional): A Jira Query Language (JQL) query to filter the search results.

6. Action (Create) - Link Issues

  • Display Name: The name you want to set for the node.

  • Source issue ID: The key of the first issue you want to link.

  • Target issue ID: The key of the second issue you want to link.

  • Link type: The type of relationship you want to establish between the two issues (e.g., "relates to," "blocks," "is blocked by").

For example, if you want to link Issue A to Issue B with a "blocks" relationship, you would enter the following information:

  • Display Name: The name you want to set for the node.

  • Source issue ID: Issue A's key

  • Target issue ID: Issue B's key

  • Link type: "blocks"

This would establish that Issue A blocks Issue B, indicating that Issue B cannot be completed until Issue A is resolved.

7. Action (Search) - Get Issue

  • Display Name: The name you want to set for the node.

  • Issue key: The key of the issue to retrieve details for.

PreviousAuthenticationNextSendGrid

Last updated 1 year ago