Create a Jira integration configuration template (integrations 1.0)

This support article refers to the historical 1.0 version of the Aha! integration with Jira.

  • If you are using the new 2.0 version of our Jira integration, reference this article.
  • If you are looking for details about integration templates for 2.0, reference this article.

The ability to create Jira integration configuration templates makes it easy for teams to roll out their Jira integrations across a full portfolio of products. With configuration templates, you can save any Jira integration you create as a template and then apply that template to future Jira integrations. Changes made to the template will update all other integrations using the template making it easy to administer a large number of integrations.

This is particularly helpful when managing credentials. A Jira admin can create the first integration with the Jira server, username, and password filled out. (Note: If you are using Jira Cloud, you will need to create an API token in Jira to use as your password.) From that point on, Aha! Product Owners can use the template to avoid the need to request the credentials every time a new integration is added. If the credentials need to be updated in the future, updating the template will update the credentials for all other integrations.

When a template is applied to a new Jira integration, the user that applied the template has the option to edit any of the configuration options they would like. This allows teams to quickly roll out configuration across multiple integrations while maintaining the flexibility to have unique options configured on a per integration basis.

How it works

You will need to be a Product Owner in Aha! to create a Jira integration through the Settings > Product area of your account. Once on the integration configuration page, click the More options button.


You will have the option to use an existing template or save the configuration you are working on as a new template. 

If you save your current configuration as a template, it will be available to use for future integrations you configure. 

If you chose to use an existing template, the configuration options from the template will be applied to your integration. Each configuration option will have a check box next to it allowing you to uncheck each field and apply a unique configuration option on a per field basis. This means you can inherit user credentials and feature mapping from a template, but define custom field mappings unique to your product as an example.

Security considerations

Since the templates allow credentials, and thus Jira access, to be used across an Aha! account, only users with access to the product containing the template will be able to apply the template.

This means if someone creates a template for "Product A" in my account, and I do not have access to "Product A," I will not be able to use the template when I configure my own "Product B" integration.

In order to use a template defined on another product, you need at least Viewer access on that product. Without full Product Owner access, the user will be able to use the template but will not have access to edit the template. This is particularly important because it allows for templates to be configured without the concern of other users editing the template and impacting integrations across the account.

Remove a template

In order to remove a template or delete an integration serving as a template, you first need to switch any integrations using that template to a different template. When viewing the template, there will be the option to view all integrations that are using the template.

Once all integrations using the template have been removed, you will have the actions menu available that allows you to delete the integration or remove it as a template.

Was this article helpful?
1 out of 1 found this helpful