Known Issues and Limitations

Currently, Issue Template for Jira - Summary & Description Templates has some known limitations. We are constantly working on to improve this app and these issues and limitations will be fixed whenever possible.

1. Access prompt when creating an issue

This issue is now fixed in latest version: Access prompt, templates limit and major upgrades

After setting up the templates, when users try to create an issue, they will be shown a prompt to authorize issue-template.

We know this is annoying and a bad UX. Unfortunately, this is caused by the underlying Atlassian API we use to build apps. This is not limited to our app. Fortunately, Atlassian is going to fix this issue soon (end of Q1 2023) and the prompt will be completely removed. You can also follow the Atlassian ticket tracking in Trello.

For now, please inform users about this prompt and the mysterious issue-template.

2. “Access denied” when trying to allow access

This issue is now fixed in latest version: Access prompt, templates limit and major upgrades

Some users see the following error message when allowing access.

We have seen this happen to users who have multiple Atlassian accounts.

You can log out from all Atlassian accounts and log in with only the account you need, and it should work as expected. The Atlassian multiple accounts feature is unfortunately a bit buggy.

3. Jira Service Management (JSM)

Issue Template for Jira only works in Jira Software and Jira Work Management (business), as extension point provided by Atlassian is currently limited to this project types.

In the future, Jira Service Management (JSM) will also be supported.

Support for Jira Work Management was added in version v5.3.0. The app might need to be updated if you are using an older version, see App Updates and Release Notes

4. Looks like Template is applied to all Issue Types

Once a template is applied, if you change to another issue type, the existing template persists if the new issue type does not have a template.

Keeping the text when changing issue type is default Jira behavior. We understand that this is confusing to users and are trying to fix. Unfortunately, it’s been a quite difficult. Until we find a reasonable fix, please use the workarounds below.

Workaround I: An workaround some users are using is that you can create empty template for other issue types. It’s not a great workaround, but can work if the issue above is confusing for your users.

Workaround II: Another option is that you could put a short instruction in description field to inform users to use the template for certain issue type only. An example template instruction would be:

⚠️ Please only use this template text for Task! Other issue types don’t have templates.

5. Jira Premium with IP Allowlist

Jira Cloud Premium customers can enable IP Allowlist feature to limit Jira access to a limited set of trusted IPs. This unfortunately breaks the apps, including Issue Template for Jira.

Fortunately, Atlassian now released the outgoing IP Address range which you add to your allowlist. The full address range can be found here: https://support.atlassian.com/organization-administration/docs/ip-addresses-and-domains-for-atlassian-cloud-products/#Outgoing-Connections

6. Subtask and creating issue from outside create window

Issue Template currently only supports creating an issue using create from, opened from top menu or using shortcut command c because of Jira API limitation. This also means Subtask issue type is not supported.

7. Error when creating issue after a template is assigned

Some users have encountered the following error when creating an issue after a template is assigned:

We encountered an error while applying UI modifications to this form.

This happens when the description field has a different renderer. The field renderer has to be Wiki Style Renderer.

If you see this error, you can go to Project Settings → Issues → Fields and change the renderer to Wiki Style Renderer for description field.