X

Overview

Events

Actions

Home > Application Reference > JIRA 2

Jump to a Section

Overview

Authorizing an Account

Authorization of Jira Software

Before connecting Jira Software to Azuqua, ask your Jira administrator to turn on the Accept Remote API calls option on the System Admin screen.

For information about configuring Jira API Tokens, click here.

  1. Enter an Account Nickname. Make this nickname unique so you can authorize multiple Jira accounts.
  2. Enter your Username and API Token.
  3. Enter your Instance URL without the “https//:“. (For example, “yourcompany.atlassian.net”)
  4. Click Create to save your configuration.

Note: If you revoke or delete your Jira API Token, you must create a new token and update all of your connections to use the new token (refer to View and Manage Connections). Jira automatically locks you out of the API if four calls are made with old or incorrect passwords/tokens. If any active flows attempt to use your old token, all calls will fail (including those that use the correct credentials). You will have to change your password to regain API access.

    Events

    • Issue Deleted

      Trigger a flow when an issue is deleted in Jira.

      Options

      • Project (drop-down): project to monitor for deleted issues
      • JQL Query (text): JQL query to indicate which issues will trigger the flow

      Output

      • Webhook
        • Raw Data (object): raw webhook data for the issue
      • Issue
        • Issue ID (text): ID of the issue
        • Self (text): URL to the issue
      • context
        • Execution ID (text): unique identifier for the execution of the flow

    • Issue Transitioned

      Triggers a Flow when an issue’s status is changed in JIRA.

      Unelss otherwise indicated, field types are text.

      Options

      • Project (drop-down): project to monitor for transitioned issues
      • JQL Query: JQL query to indicate which issues will trigger the flow

      Output

      • Webhook
        • Raw Data (object): raw webhook data for the issue
      • Issue
        • Issue ID: ID of the issue
        • Self: URL to the issue
      • Transition
        • Transition ID (number): ID of the transition
        • From: original status of the issue
        • To: new status of the issue
      • User
        • Name: username of the user who made the transition
        • Display Name: display name of the user who made the transition
        • Active (true/false): indicator iff the user is active
        • Email: email address of the user who made the transition
      • context
        • Execution ID: unique identifier for the execution of the flow

    • Issue Updated

      Trigger a Flow when an issue is updated in Jira.

      Unless otherwise indicated, field types are text.

      Options

      • Project (drop-down): project to monitor for new issues
      • JQL Query: JQL query to indicate which issues will trigger the flow

      Output

      • Webhook
        • Raw Data (object): raw webhook data for the issue
      • Issue
        • Issue ID: ID of the issue
        • Self: URL to the issue
      • context
        • Execution ID: unique identifier for the execution of the flow

    • Issue Updated - Polling

      Triggers a Flow when an issue is updated in JIRA (polling method).

      Unless otherwise indicated, field types are text.

      Options

      • Project (drop-down menu): project to monitor for updated issues

      Output

      Click the Settings icon at the bottom of the card to choose output fields.

      • Issue
        • Issue ID: unique ID of the issue
        • Self: URL to the issue
        • Key: issue key
      • context
        • Execution ID: unique identifier for the flow execution

    • New Comment

      Trigger a Flow when a new comment is created in Jira.

      Unless otherwise indicated, field types are text.

      Options

      • Project (drop-down): project to monitor for comments

      Output

      • Webhook
        • Raw Data (object): raw webhook data for the comment
      • Issue
        • Issue ID: ID of the issue the comment was added to
      • Comment
        • Comment ID: ID of the comment
        • URL: URL to the comment
        • Body: content of the comment
        • Created Date (date and time): timestamp when the comment was posted
      • Author
        • Name: username of the comment’s author
        • Display Name: display name of the comment’s author
        • Active (true/false): indicator if the user is active
      • context
        • Execution ID: unique identifier of the flow execution

    • New Issue

      Trigger a flow when a new issue is created in Jira.

      Unless otherwise indicated, field types are text.

      Options

      • Project (drop-down): project to monitor for new issues
      • JQL Query: JQL query to indicate which issues will trigger the flow

      Output

      • Webhook
        • Raw Data (object): raw webhook data for the issue
      • Issue
        • Issue ID: ID of the issue
        • Self: URL to the issue
      • context
        • Execution ID: unique identifier for the execution of the flow

    • New Issue - Polling

      Triggers a Flow when a new issue is created in JIRA (polling method).

      Unless otherwise indicated, field types are text.

      Options

      • Project (drop-down menu): project to monitor for new issues

      Output

      Click the Settings icon at the bottom of the card to choose output fields.

      • Issue
        • Issue ID: unique ID of the issue
        • Self: URL to the issue
        • Key: issue key
      • context
        • Execution ID: unique identifier for the flow execution

    • New Project

      Triggers a Flow when a project is created in JIRA.

      Unless otherwise indicated, field types are text.

      Output

      • Webhook
        • Raw Data: raw webhook data with the project information
      • Project
        • Key: short identifier for the project
        • Project ID (number): ID of the project
        • Lead Username: username of the project lead
        • Name: name for the project
        • API Resource URL: API Resource URL for the project
        • URL: URL for the project
      • Context
        • Execution ID: ID for the flow execution

    • New Work Log Entry

      Trigger a Flow when a new work log entry is made in Jira.

      Unless otherwise indicated, field types are text.

      Options

      • JQL Query (text): JQL query to determine the issues returned

      Output Fields

      • Webhook
        • Raw Data (object): raw webhook data for the work log
      • Entry
        • URL: URL for the work log entry
        • Comment: comment on the work log
        • Started At (date and time): timestamp when the work was started
        • Time Spent: time spent working
        • Time Spent (seconds) (number): time spent working, in seconds
        • Worklog ID (number): ID for the work log
        • Parent Issue ID (number): ID of the parent issue the work is on
      • Visibility
        • Type: type of visibility for the work log entry
        • Level: level of visibility for the work log entry
      • Author
        • Name: username of the author
        • Display Name: display name of the author
        • Active (true/false): indicator if the author is active
      • Context
        • Execution ID: unique identifier for the flow execution

    • Project Updated

      Trigger a Flow when a project is updated in Jira.

      Unless otherwise indicated, field types are text.

      Output

      • Webhook
        • Raw Data: raw webhook data with the project information
      • Project
        • Key: short identifier for the project
        • Project ID (number): ID of the project
        • Lead Username: username of the project lead
        • Name: name for the project
        • API Resource URL: API Resource URL for the project
        • URL: URL for the project
      • Context
        • Execution ID: ID for the flow execution

    Actions

    • Add Issue to Sprint

      Add an existing issue to a sprint in Jira. The issue can be identified by the key (in the issue URL https://yourdomain.atlassian.net/projects/HT/issues/HT-22, HT-22 is the key) or mapped from a Read Issue or Create Issue card.

      Input

      • Sprint
        • Sprint ID (text): ID of the sprint
      • Issues
        • Issue IDs or Keys (list of text): ID or key of the issue to add to the sprint

      Output

      There is no output for this card.

    • Build Issue Object

      Build an issue object for use with "Create Issues"

    • Create Comment

      Create a comment on an issue in Jira. The issue can be identified by the key (in the issue URL https://yourdomain.atlassian.net/projects/HT/issues/HT-22, HT-22 is the key) or mapped from a Read Issue or Create Issue card.

      Unless otherwise indicated, field types are text.

      Input

      • Issue
        • ID or Key: ID or key of the issue you want to comment on
      • Comment
        • Body: content of the comment

      Output

      • Response
        • Status Code (number): Status of the comment attempt. Status codes are defined here.

    • Create Issue

      Create a new issue in Jira.

      Unless otherwise indicated, field types are text.

      Options

      • Project (drop-down): List of existing projects in your JIRA account. Select All Projects to enter the project name as an input.
      • Issue Type (drop-down): Type of issue to create. Select All Issue Types to use the issue type as an input.

      Note: Choose All Projects or All Issue Types to run different types each time the flow is executed.

      Input

      Input fields are dynamically generated from your Options selections.

      • Project: project you selected in the Projects drop-down
      • Fields
        • Issue Type: type of issue you selected in the Issue Type drop-down
        • Summary: summary of the issue
        • Component/s (list of text): Container or subsection of the project, used to group issues. Setting a default assignee for a component will override the project’s default assignee.
        • Description: A description of the issue. To send an email to a user, mention them (@ + Jira username) here.

      Output

      • Issue
        • Key: issue key or identifier
        • Issue ID: unique ID of the issue
        • URL: URL of the issue
        • API Resource URL: URL directing to the API resource

    • Create Issues

      Create multiples issues at once

    • Create Project

      Create a project in Jira.

      Field types are text.

      Input

      • Project
        • Name: name for the project
        • Key: short identifier for the project
        • Description: description of the project
        • Lead Username: username of the lead for the project

      Output

      • Project ID: ID of the project
      • Key: short identifier for the project (created above)
      • URL: URL for the project
      • API Resource URL: API Resource URL for the project

    • Create Sprint

      Create a sprint on a Jira board.

      Unless otherwise indicated, field types are text.

      Options

      • Board (drop-down): available Jira boards

      Input

      • Sprint
        • Name: name of the sprint
        • Start Date: start date of the sprint (YYYY-MM-DDTHH:MM:SS.MMMZ format, for example: 2017-07-21T22:33:58.411Z)
        • End Date: end date of the sprint (YYYY-MM-DDTHH:MM:SS.MMMZ format, for example: 2017-07-21T22:33:58.411Z)
        • Goal: goal for the sprint

      Output

      • Sprint ID (number): ID for the new sprint

    • Custom API Action

      Make an authenticated HTTP request to the JIRA API

    • Delete Issue

      Delete an issue in Jira.

      Input

      Output

      • Response
        • Status Code (number): status of the attempt (status codes are defined here)

    • Delete Project

      Delete a project in Jira.

      Input

      Output

      • Response
        • Status Code (number): status of the attempt (status codes are defined here)

    • Delete Sprint

      Delete a future sprint in Jira.

      Input

      • Delete By
        • Sprint ID (number): ID of the sprint to delete

    • Download Attachment

      Download a file from Jira.

      Input

      • Attachment
        • Attachment ID (text): ID of the attachment to be downloaded

      Output

      • Attachment
        • File Content (file): contents of attachment

    • Dynamic Auth Custom API Action

      Make a custom API request to the JIRA API with dynamic authentication

    • Edit Sprint

      Update the details of a sprint in Jira.

      Input

      • Update By
        • Sprint ID (number): ID of the sprint
      • Sprint
        • Name (text): name of the sprint
        • State (drop-down): state of the sprint (closed or active)
        • Start Date (text): start date of the sprint (format: YYYY-MM-DDTHH:MM:SS)
        • End Date(text): end date of the sprint (format: YYYY-MM-DDTHH:MM:SS)
        • Goal (text): goal of the sprint

    • List Issues

      List all issues in a Jira project.

      Options

      • Project (drop-down): List of existing projects in your JIRA account. Select All Projects to enter the project name as an input.
      • Issue Type (drop-down): Type of issue to create. Select All Issue Types to use the issue type as an input.

      Note: Choose All Projects or All Issue Types to run different types each time the flow is executed.

      Input

      • Options
        • Issue Type ID or Name (text): type ID or name of the issue (if All Issue Types or Insert ID was selected)
        • Project Name or ID (text): name or ID of the project (if All Projects or Insert ID was selected)
        • Limit (number): maximum number of issues to retrieve
        • Offset (number): number of issues that will be skipped before returning the list of issues

      Output

      • Result
        • Issues (list of objects): list of the issues found in the project

    • List Projects

      List all Jira projects and their information.

      Unless otherwise indicated, field types are text.

      Input

      There are no input fields for this card.

      Output

      • Result
        • Projects (list of objects)
          • Key: unique project key
          • Project ID: ID of the project
          • Description: description of the project
          • API Resource URL: URL to the API resource for the project
          • URL: URL to the project
          • Category: category of the project
          • Issue Types (list of text): list of issue types
          • Lead Username: username of the project lead
          • Lead Display Name: display name of the project lead
          • Lead Active (true/false): indicator if the lead is active

    • List Work Logs

      List all work logs for an issue in Jira.

      Input

      Output

      • Result
        • Work Logs (list of objects): dynamically generated list of all existing work logs

    • Log Work

      Log work on an issue in Jira.

      Note: To edit the visibility of Azuqua, use the Jira HTTP Request card with System Admin credentials.

      Input

      • Issue
      • Worklog
        • Comment (text): comment about the logged work
        • Time Started (text): timestamp when the work began, formatted using ISO UTC (2016-09-07T16:55:25.670Z), offset notation (2016-09-07T16:55:25+00:00), or the Jira expected format (2017-06-16T02:48:07.240+0000)
        • Time Spent (seconds) (number): amount of time spent on the issue (in seconds - 3600 for one hour)

      Output

      • Response
        • Status Code (number): status of the attempt (status codes are defined here)

    • Read Issue

      Read an issue in Jira.

      Unless otherwise indicated, field types are text.

      Options

      • Project (drop-down): List of existing projects in your JIRA account. Select All Projects to enter the project name as an input.
      • Issue Type (drop-down): Type of issue to create. Select All Issue Types to use the issue type as an input.

      Input

      Output

      • Issue
        • Issue ID: unique ID of the issue
        • Self: URL to the issue
        • Key: unique key of the issue

    • Read Project

      Read a project in Jira.

      Unless otherwise indicated, field types are text.

      Input

      Output

      • Project
        • Key: unique project key
        • Project ID (number): ID of the project
        • Name: name of the project
        • Type: type of project
        • URL: URL to the project
        • API Resource URL: API Resource URL for the project
        • Description: description of the project
        • Assignee Type: types of assignees in the project
        • Issue Types(list of text): list of the issues in the project
      • Project Lead
        • Username: username of the project lead
        • Display Name: display name of the project lead
        • Active (true/false): indicator if the project is active

    • Read Sprint

      Use the Sprint ID to read a sprint in Jira.

      Input

      • Read By
        • Sprint ID (number): ID of the sprint to read

      Output

      • Sprint
        • Name (text): name of the sprint
        • State (text): state of the sprint (Closed or Future)
        • Start Date (date): start date of the sprint
        • End Date (date): end date of the sprint
        • Complete Date (date): date that the sprint was completed (if Closed)
        • Board ID (number): ID of the board that the sprint is on
        • Goal (text): goal of the sprint

    • Read Sprint Issues

      Return a list of issues in a Jira sprint.

      Input

      • Read By
        • Sprint ID (number): ID of the sprint
        • Start At (number): offset of the data returned
        • Max Results (number): maximum number of issues to return
        • JQL Query (text): JQL query to identify issues

      Output

      • Result
        • Issues (list of objects): dynamically generated list of issues in the sprint

    • Read User

      Read a user in Jira.

      Unless otherwise indicated, field types are text.

      Input

      • User
        • Key: unique identifier of the user (usually the username)

      Output

      • User
        • Display Name: display name of the user
        • Username: username of the user
        • Email Address: user’s email address
        • Active? (true/false): indicator if the user is active

    • Search Issues

      Search for an issue in Jira.

      Unless otherwise indicated, field types are text.

      Options

      • Project (drop-down): List of existing projects in your JIRA account. Select All Projects to enter the project name as an input.
      • Issue Type (drop-down): Type of issue to create. Select All Issue Types to use the issue type as an input.
      • Result Set (drop-down): all match issues or the first match that is found

      Input

      • Options
        • Offset (number): Offset for the results. If the card finds 50 issues and you want to return the last 20, your offset is 30 and your max result is 20.
        • Max Results (number): maximum number of results to return
      • Search By
        • Assignee: assignee of the issue
        • Category: category of the issue
        • Comment: comment on the issue
        • Created: timestamp when the issue was created
        • Creator: username of the user who created the issue
        • Description: description of the issue
        • Due Date: date when the issue is due
        • Last Viewed: last time the issue was viewed

      Output

      • Issue
        • Key: key of the issue
        • Issue ID: unique ID of the issue
        • API Resource URL: URL of the API resource for the issue
        • URL: URL of the issue

    • Search Issues by JQL

      Use a Jira Query language (JQL) query to get a list of issues in Jira.

      Options

      • Enviroment (drop-down): environment where the Jira instance is hosted (On-Premise or Cloud)

      Input

      • Search By
        • JQL Query (text): JQL query to determine the issues returned
        • Limit (number): maximum number of issues returned
        • Offset (number): offset for the list of issues returned

      Output

      • Result
        • Issues (lists of objects): issues returned by the query
        • Key (text): unique issue key
        • Issue ID (number): unique ID of the issue
        • URL (text): URL of the issue
        • API Resource URL (text): URL to the API resource for the issue

    • Search Projects

      Search for a project in Jira.

      Unless otherwise indicated, field types are text.

      Options

      • Result Set (drop-down): all matching results or the first matching result

      Input

      • Project
        • Name: name of the project
        • Category: category of the project
        • Lead Username: username of the project lead
        • Lead Display Name: display name of the project lead

      Output

      • Project
        • Name: name of the project
        • Key: key of the project
        • Project ID: unique ID of the project

    • Search Projects by Issue

      Search for a Jira project with an issue ID or key.

      Field types are text.

      Input

      Output

      • Project
        • Project ID: ID of the project
        • Key: project key
        • URL: URL for the project
        • API Resource URL: URL of the API resource for the project

    • Search Users

      Search for a username in Jira.

      Unless otherwise indicated, field types are text.

      Options

      • Result Set (drop-down): all username matches or the first username to match your search query

      Input Field

      • User
        • Query: name, username, or email address to search (for example, sarah or sarah@companyname.com)

      Output Field

      • Username: username of the matched user (determined by the Result Set selection)

    • Transition Issue

      Change the status of an issue in Jira.

      Unless otherwise indicated, field types are text.

      Input

      • Transition
        • Issue ID or Key: ID or key of the issue
        • Transition To: new status of the issue (In Progress, To Do, or Done)
        • Comment: comment about the issue

      Output

      • Response
        • Status Code (number): status of the attempt (status codes are defined here)

    • Update Issue

      Update an issue in Jira.

      Unless otherwise indicated, field types are text.

      Options

      • Project (drop-down): List of existing projects in your JIRA account. Select All Projects to enter the project name as an input.
      • Issue Type (drop-down): Type of issue to create. Select All Issue Types to use the issue type as an input.

      Note: Choose All Projects or All Issue Types to run different types each time the flow is executed.

      Input

      Input fields are dynamically generated from your Options selections. If you do not provide the project name or the issue type as an option, enter them here.

      • Issue
      • Fields
        • Issue Type: type of issue you selected in the Issue Type drop-down
        • Summary: summary of the issue
        • Component/s (list of text): Container or subsection of the project, used to group issues. Setting a default assignee for a component will override the project’s default assignee.
        • Description: A description of the issue. To send an email to a user, mention them (@ + Jira username) here.

      Output

      • Response
        • Status Code (number): status of the attempt (status codes are defined here)

    • Update Project

      Update a project in Jira.

      Unless otherwise indicated, field types are text.

      Input

      • Project
        • ID or Key: ID or key of the issue to edit. You can use the Search Projects card or Search Projects by Issue card to find this information.
      • Fields
        • Key: new key for the project
        • Name: name of the project
        • Description: description of the project
        • Lead Username: username of the project lead

      Output

      • Response
        • Status Code (number): status of the attempt (status codes are defined here)

    • Upload Attachment

      Attach a file to an issue in Jira.

      Input

      Output

      • Attachment
        • Attachment ID (text): ID of the attachment

    • Create Version

      Create a version in Jira.

      Unless otherwise indicated, field types are text.

      Input

      • Version
        • Name: unique name of the version
        • Release Date: release date of the version, ISO 8601 format (yyyy-mm-dd)
        • Start Date: start date of the version, ISO 8601 format (yyyy-mm-dd)
        • Project ID (number): ID of the project to which this version is attached
        • Description: description of the version
        • Archived (true/false): indicator if the version is archived

      Output

      • Response (string): response from Jira API
        • Status Code (number): status of the Jira API response
        • Self: link to the version
        • ID: version ID
        • Description: description of the version
        • Name: unique name of the version
        • Archived (true/false): indicator if the version is archived
        • Released (true/false): indicator if the version is released
        • Project ID (number): ID of the project to which this version is attached

    • Update Version

      Update a version in Jira.

      Unless otherwise indicated, field types are text.

      Input

      • Version
        • ID: ID of the version to update
        • Name: unique name of the version
        • Release Date: release date of the version, expressed in ISO 8601 format (yyyy-mm-dd)
        • Start Date: start date of the version, expressed in ISO 8601 format (yyyy-mm-dd)
        • Description: description of the version
        • Archived (true/false): indicator if the version is archived
        • Released (true/false): indicator if the version is released
        • Move Unfixed Issues To: URL of the self link where unfixed issues are moved when a version is released

      Output

      • Response (object): values returned from the Jira API
        • Status Code: status of the response from Jira API
        • Self: link to the version
        • ID (number): ID of the version
        • Description: description of the version
        • Name: unique name of the version
        • Archived (true/false): indicator if the version is archived
        • Released (true/false): indicator if the version is released
        • Project ID: ID of the project to which this version is attached