Integrate with Jira to share tasks between Jira and Agiloft seamlessly. For example, if your support users manage tickets in Agiloft and pass them to developers using Jira, you can configure your system to easily send support tickets to Jira and back.
For example, let's create a new task in Agiloft and sync it to Jira. Notice the task is assigned a Pkey by Jira, so the Pkey doesn't populate until the task is received by Jira.
In this example, the sync is done manually, but usually the sync would be done automatically behind the scenes. You might automatically sync all Jira tasks at a set time interval, or trigger a sync based on an action in time-sensitive workflows.
- Create or identify a Jira administrator account to use with Agiloft.
- Have the Jira address ready.
Enable Jira Integration
When you enable Jira integration, three tables are automatically created in your system:
- Jira Issues
- Jira Issue Types
- Jira Projects
Each table correlates to the issues, issue types, and projects in Jira, respectively.
- In your Agiloft knowledgebase, go to Setup > Integration.
- Under Jira Integration, click Deploy.
- Click OK in the warning that appears and wait for the tables to be created. When the tables are ready, the sync wizard opens automatically.
- In the sync wizard, review the settings on the General tab and make changes as needed. Most settings are appropriate for Jira by default, but you might want to change the sync name or these integration settings:
- Directions. By default, the system both sends and receives data with Jira. If you need to only send or only receive data from Jira, select the appropriate option.
- Conflicts. By default, if Agiloft and Jira have conflicting information, the Jira information is used. You can choose instead to use the Agiloft information, the most recent information, or to duplicate the records.
- Click Next to open the ESA Settings tab.
- Complete the fields with the Jira address and login credentials.
- Click Next to open the Mapping tab.
Agiloft is automatically mapped to Jira using the three tables listed above: Jira Issues, Jira Issue Types, and Jira Projects. Records are matched by the ID field in each table, and sync is allowed to create and update records in both Agiloft and Jira. In the Jira Issues table, sync can also delete records in both systems. IDs are generated by Jira, and no saved search filters are used.
In most cases, this configuration is appropriate for Jira integration. If you need to modify any of the default behaviors, or if you want to review the specific field mapping, click Edit Mapping next to the table you need to modify and make the appropriate changes.
- Make any necessary adjustments to the mappings and then click Next twice.
- On the Running tab, specify how Jira sync can be initiated. By default, all sync options are allowed. You must have the By Actions (Rules/Workflow) option selected to use sync automation.
- Click Finish.
You can use a time-based rule to setup an automated sync process.
To automate the sync process this way, your Jira configuration must allow actions to run the sync. To check your setting, go to Setup > Sync and open your Jira configuration. Click Next until you reach the Running tab. Confirm that the By Actions (Rules/Workflow) option is selected.
To set up time-based sync automation:
- Go to Setup > Rules > New.
- In the Rule wizard, use these settings:
- On the General tab, enter a name and select a table.
- On the Rule Type tab, select At selected time intervals.
- On the Condition tab, select "Run once per scheduled time interval."
- On the Schedule tab, set Apply Rule to the appropriate time interval.
- On the Action tab, click the Create Sync Action button.
- In the Sync Action wizard:
- Enter an action name.
- In the External System ID field, click the search icon to see a list of configurations. Select the Jira configuration.
- Click Finish.
- Click Finish.
After that, the sync process will run based on the interval set on the Schedule tab.
The sync will operate for all tables mapped in the sync configuration, regardless of which table contains the rule. If you need to sync some tables separately, you will need to create a separate configuration for each table and use them in different sync actions. You should be careful with multiple Jira syncs that you do not create conflicts with existing mappings.