![]() After selecting the account you'd like to use you'll need to pick the project you like the updated information to be sent to as well as the Issue ID or key. If this is the first time you are connecting to a Jira account, then follow the instructions above. Next, you'll need to choose a Jira Server account to connect to. The first step is to add the "Update issue" action either in a new automation or as another action step in an existing automation. ![]() However, there are a few things to be aware of during the setup process. The Jira Server / Data Center "Update issue" automation action has a similar setup process to the Jira Server / Data Center "Create issue" action covered above. Otherwise, if the test looks correct, then you can turn the automation on by toggling the button near your automation's name. If you need to make adjustments, then remember to test the trigger step of the automation if you change anything in your Airtable base. Now is the right time to check that the automation is porting over the correct information into Jira. Click the "Test action" button at the bottom of the setup window. Once you've configured the various fields of your automation the way you like it's time to test the action step. This includes the Description, Reporter, Assignee, Status, Labels, and Other issue data fields. In the example below, you'll see that the Summary field can be either a static or dynamic (based on the record in Airtable) field value.ĭepending upon your setup, you can either stop here or continue to build in static or dynamic values into the fields below. All three of these fields are required to build a working automation. Once your account is connected, you can move on to choosing the Project where the issues will be created as well as the Issue type and Summary. Clicking "Allow" should close the authentication window and permit you to continue with the automation setup process. If you successfully log in, then you should see an option to "Allow" Airtable read and write access. ![]() This will open a pop-over window where you should be able to log into your account and connect to a specific server instance. Click on the plus button below to learn more about this process. Alternatively, if this is your first time connecting to Jira Server on Airtable or if you are not seeing the expected account, then you'll need to connect to a new account. Here you can choose a previously connected Jira Server account. Then, move on to connecting to a Jira Server account. So, we will use the "When a record matches conditions" trigger.Īs always, be sure to successfully test whichever trigger you end up using in your automation.Īfter your trigger is configured and tested, you can start configuring your Jira Server / Data Cetner action.Īt this point, you can choose to add a description of this automation action so that other Airtable collaborators know what this action does. In our example, checkbox fields are being used to create and/or update the issue in Jira. The trigger you choose to use for the automation is contingent upon the way that your Airtable base has been set up. Choose a triggerįor either updating or creating a Jira Server / Data Center issue, you will start the automation configuration process by adding a new custom automation and choosing a trigger. Consider how implementing both features in your Airtable base may help to keep both services updated and matching. Jira Server / Data Center automation actions pair well with our Jira Server / Data Center Sync integration feature.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |