+

Jira Connector Reference

Jira is a powerful project management tool and ticketing system used to help users plan, track, release, and report product issues in order to improve development.

To use Jira Connector with Composer, you must have the Administrator Jira global permission. For more information, see the Jira documentation.

Connections

To connect to a system, whether it is a source of data or the target where you are sending data, you must create a connection with that system’s required credentials. You typically connect to different systems within a flow and can reuse each connection every time you need to connect.

This system requires the following credential information for its connections:

Connection Name

Enter a connection name that will help you remember the details of this connection. You can reuse connections multiple times in a single flow, and in more than one flow, and the credentials are hidden after you create the connection. Therefore, it’s helpful to provide a name that easily identifies this connection from others.

Only you can see the connection. Other users in your Composer app must create their own connections.

Username

The OAuth username that you use to log in to Jira.

Password

The OAuth password that you use to log in to Jira.

Triggers

Each flow starts with a scheduler that specifies a time span for how frequently the flow starts or with a trigger that you define, such as "each time a new record is created." Triggers provide multiple options related to the data in your system.

Triggers execute every ten minutes.

This system provides the following trigger options:

New issue with Custom Fields

Checks for a new issue with Custom fields created in Jira.

New issue with Standard Fields only

Checks for a new issue with Standard fields created in Jira.

Update issue with Custom Fields

Checks for updated issues with Custom fields in Jira.

Update issue with Standard Fields only

Checks for updated issues with Standard fields in Jira.

Actions

After you connect to a system and define the trigger or configure a scheduler, you define the actions that the flow performs, such as copying a record from Workday to Salesforce. The actions you can perform depend on which system you are connected to.

This system provides the following actions:

Create issue with custom fields

Creates a new issue within the selected project. Provide a value for the following fields:

  • Project

  • Key

  • Summary

  • Type

  • Status

  • Priority

Update issue with custom fields

Updates specified Custom field values. Provide a value for the following fields:

  • Issue ID or Key

  • Notify Users

Update issue with standard fields only

Updates specified Standard field values. Provide a value for the following fields:

  • Issue ID or Key

  • Notify Users

Assign user to issue

Assigns a user to a specified issue. Provide a value for Issue ID or Key.

Add watcher to issue

Adds a watcher to an existing Jira issue. Provide a value for Issue ID or Key.

Get issue

Returns details for a specific issue. Provide a value for Issue ID or Key.

Add comment to issue

Creates and adds a comment to an existing issue. Provide a value for the following fields:

  • Issue ID or Key

  • Comment Text

Get account IDs for users

Returns the account IDs for the users specified in the key or username parameters. You can specify multiple key or username parameters.

Custom Fields

Using MuleSoft Composer, you can access Standard custom field values in Jira for actions and triggers that you set in the Jira issue.

Was this article helpful?

💙 Thanks for your feedback!

Edit on GitHub