Airtable automation actions: Jira Cloud

Follow the steps outlined in this support article.

For either of the Jira Cloud actions, you’ll need to set up the trigger that will tell the automation when to run and which record to use to either update or create a Jira issue.

• For this example, we’ll be using a table we created to keep track of user-submitted bugs. Our ideal workflow is when a new record enters our New Bugs view it will automatically create a Jira issue with the same information.

• We will use the “When record enters a view” trigger to ensure that any record that enters this view will trigger our new Automation.

• Next, you’ll choose the Jira Cloud action that best suits your use case

• After your trigger is configured and tested, you can start configuring a Jira Cloud action.

• You’ll be prompted to select or connect your Jira account.

• Once your account is connected, the dropdown options for Site, Project, and Issue Type will be pre-populated based on your Jira account. Click the dropdown menus and select the appropriate option for your use case. For our example automation, we’ll use the “Bug” Issue type.

After this initial account configuration is set, you can then customize the details for the new Jira issue you’ll be creating. The fields you can customize include:

• Summary

• Description

• Labels

• Reporter (contingent on your Jira account permissions)

• Assignee (contingent on your Jira account permissions)

• Status

• Other Issue Data - The subfields listed under the “Other Issue Data” input will allow you to configure custom fields for the currently selected issue type.

For our bug tracking example, we set up the below configuration for our new Jira issue.

After configuring the action’s options, we’ll run a test to ensure everything is set up properly so far. You can see more information about the test, and your newly created Jira issue, by clicking on the arrow to the right of the test status.

• After your trigger is configured and tested, you can start configuring a Jira Cloud action.

• You’ll be prompted to select or connect your Jira account.

• Watch a 100-second walkthrough

• In order to set up the “Jira Cloud Update Issue” action, you will need to have the Jira Issue IDs for the issues you are looking to update. You can either track these in an Airtable field manually or utilize the IDs captured in an earlier step of the automation as described below.

Here is the trigger we’ll be for this new automation using our previous bug tracking example:

You’ll want to ensure that any updates to the table are reflected in the Jira issue we just made. Once the trigger is set up, we can create our “Jira: Update Issue” action. The initial configuration steps are very similar to the steps we took when creating a new Jira issue. You’ll need to select the Jira Account, Site, and Project you’d like to update.

Choosing an “Issue Type” for updating an existing Jira Issue is optional, but will give you access to any type-specific fields.

You’ll then need to enter the Jira Issue ID or Key that you’d like to update. This is where we will utilize the Jira Issue ID field we previously created on our example table.

Next, you can go about picking the fields you’d like to update on the Jira issue from the prefilled list.

The last step, as always, is to test your new automation to ensure everything is configured correctly before turning your new automation on. In our example of utilizing both Jira actions in an automation, turning on the automation and adding a new record to the table will now create a corresponding Jira issue and will update our record with the ID of that issue.

As updates are made in Airtable to the individual Issue’s record, the automation will additionally update the Issue in Jira.

Jira Server automation actions are covered in this support article.

Yes, but only string (text), single select, and multiple select fields. Some types of custom fields, particularly those that come from plugins, may not be supported.

Neither of Airtable’s Jira Cloud automation actions supports creating sub-tasks.

We support linking an issue to a parent issue, but other types of issue links are not supported.

To connect to another Jira site, you can select “Connect new account” from the account selection menu, and select the desired site as part of the authorization process.

This is a bit more complicated due to the Jira account authorization process. To add a second Jira account, you have to first log out of Atlassian in the same browser. Then, select Connect new account from the account selection menu and log in via the desired Atlassian account.

If the Jira account for a related automation is deactivated or disconnected, then the automation will cease to work until a new Jira account is connected and configured.

The selected project and issue type in Jira does not allow the “Reporter” field to be set. More context from a Jira community post here.

No. However, one workaround would be to use a custom text field for an attachment URL, so that the attachment can be accessed from or referenced in Airtable.