Airtable automation actions: Jira Server / Data Center

T o start creating an automation, from the open base of your choice click on Automations in the upper left corner of your screen to open the automation configuration window. Click the + Create automation option to begin the setup process. If you would like, you can rename the automation right away to make it easier to understand what it does.

N ext, you will need to click + Add trigger option. Once clicked, the available triggers will display for you to choose from. Click here to learn more about all available automation triggers . Once you have configured and tested the trigger, you can move on to the next step.

1. Click the + Add advanced logic or action option.

2. Scroll down in the menu that appears and find the “Jira Server/Data Center” section.

3. While hovering over that option, click the Create issue or Update issue option. Depending on which option you choose, consult the next steps below.

Note

The values you configure in the next portion of the automation’s copnfiguration can sometimes be static (same information included with every update sent to Jira) or dynamic (changes depending upon the information being held in the corresponding Airtable record). Keep that in mind, when building out the Jira Server automation action of your choice below.

1. Feel free to enter a description of what the action will do. You can always add one later if you prefer to skip this step.

2. Under “Configuration,” click the dropdown below the “Jira Server/Data Center” section. From here, either select a previously connected account or connect a new account. More information on managing connected accounts is available here.

3. Once you have connected an account, select the “Project” where you want to create or update an issue.

4. After choosing the project, choose the “Issue type” that will be created.

5. Now, you can start configuring the “Summary” section. Enter a static summary or click the cogwheel icon and the  Dynamic option to utilize a token from a field containing summary information from an earlier automation step referenced in the underlying Airtable base.

6. Next, you’ll configure a “Description” of the issue. This description can include a mix of static information including text and emojis, as well as dynamic information from records in Airtable using the blue and white plus button to add those tokens.

7. Next up, you will likely want to choose the following additional fields:

   1. Reporter - Choose a static reporter to attach to each created issue or leave this field blank.

   2. Assignee - Choose a static assignee to attach to each created issue or leave this field blank.

   3. Status - Select between Todo, In progress, or Done as a static status each time an issue is created. You may also insert a status field’s information, stored in Airtable, to dynamically cause this value to change depending upon the Airtable record used to create the issue in Jira.

   4. Labels - Insert labels for each created Jira issue statically or dynamically.

   5. Other issue data - The options in this portion of the configuration will vary by each project, since some projects will contain fields that others don’t.

8. After your action configuration looks the way you want it to, click Test action to ensure the issue to be created or updated is looking the way you want it to. Feel free to adjust the configuration before moving to the final step below.

1. Feel free to enter a description of what the action will do. You can always add one later if you prefer to skip this step.

2. Under “Configuration,” click the dropdown below the “Jira Server/Data Center” section. From here, either select a previously connected account or connect a new account. More information on managing connected accounts is available here.

3. Once you have connected an account, select the “Project” where you want to update the issue.

4. Next, you may optionally choose to select an issue type from the dropdown menu that appears.

5. After choosing the project, you can start configuring the “Issue ID or key” section. Here, you can either enter a static ID/Key or click the cogwheel icon and the  Dynamic option to utilize a token from a field containing ID/Key information from an earlier automation step referenced in the underlying Airtable base.

6. Next, you’ll configure which fields (Summary, Description, Labels) will be updated. You can configure the action to include just 1 field, a mix of 2 fields, or all 3 fields.

7. After your action configuration looks the way you want it to, click Test action to ensure the issue to be created or updated is looking the way you want it to. Feel free to adjust the configuration before moving on to the final step below.

Note

As a reminder, if you need to append a new field in your table to hold keys or IDs, then you'll need to retest the trigger step so that the automation uses the most current state of your base.

Again, be sure to test all of the steps in the automation that you are building. Once every part of the automation has tested successfully, you’ll likely be ready to turn the automation on. Find the red colored “OFF” toggle and click it so the automation now appears as “ON” in green.

The Jira Server / Data Center integration on Airtable uses OAuth to authenticate requests from individual users in your Jira Server instance. The OAuth consent screen will look like this:

Airtable will only have access to the issues and filters that the user who connected the Jira account has access to. If the user who connected a Jira account has their Jira or Airtable account deactivated, the sync will stop working.

Note

There is no separate plugin or app that needs to be installed on the user’s Jira instance. The data that we retrieve from Jira’s API is transmitted securely via HTTPS and will not be used for any purpose other than the synced table.

Airtable integrates with Jira Server / Data Center through OAuth 1.0a. You do not need to provide scopes and the integration’s permissions will match the individual’s permissions granted in Jira Server. For more information, check out Jira’s documentation here.

The tokens are transmitted between Airtable and Jira’s servers securely via HTTPS. On Airtable’s side, the tokens are stored in databases that are encrypted at rest. 

Support documentation about Jira Cloud automation actions can be accessed here. 

Yes, but only string fields. Some types of custom fields, particularly those that come from plugins, may not be supported.

Neither of our Jira Server actions support creating sub-tasks.

We currently support linking an issue to a parent issue, but other types of issue links are not currently 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.