Limitations & Workarounds


App Constraints (Storage/API)

Project Templates for Jira relies solely on the Atlassian Forge Storage API for storing your template settings. The API ensures that there is no data egress, as all information remains within your instance. However, storage capacity restrictions apply. To prevent any functional issues during use, we've established specific limits within our app:

  • Up to 50 project templates allowed

  • Up to 50 predefined project role assignments, components, version & issues per project template

  • Up to 500 cloned issues per project template

  • JQL filter for cloned issues capped at 5,000 characters

  • Summaries & names capped at 250 characters

  • Descriptions capped at 1,000 characters

  • Issue descriptions capped at 5,000 characters

  • API Pagination limitation: Only the first 2000 projects, components, versions & project role actors are considered in dropdown selections and during cloning.

Please let our support know, if any of those constraints is blocking you.

Workaround Clone Custom Board

Our app provides the functionality to create basic board. Sadly, there are no official APIs to clone custom boards or update board settings (Feature request). Therefore, we can not provide the functionality to clone custom boards as part of the project template.
However we are able to create basic Kanban/Scrum boards with a custom filter for the new project that you can use to skip step 5-8 of the following list.

  1. In the top navigation, click on Search → click on Boards

2. In the board overview, click on Copy in the dropdown.

This creates a copy of the existing board, but still in the same project & the same issue filter.

3. Click on Edit settings on the new board. ('Copy of …')

4. Rename the board and change the location to the new project

5. The board still uses the same shared filter with the old board. Click on ‘Edit Filter Query’
Note: If you created the project with a Basic board provided by template, you can use the already created filter and skip to step 8.

  • The filter name will be Filter for <PROJECT_KEY> board

  • The filter owner will be the creator of the project.

  • The filter will be shared with the new project

  • The filter JQL will be

project = <PROJECT_KEY> ORDER BY Rank ASC

Otherwise, follow steps 5-8 to create a new filter and start with Edit Filter Query

6. Change the filter parameter project to the new project and click on Save as to create a new filter with an updated name for the new project.

 

7. Update the filter permission to include the new project.

Select Project New created projectAdd Save

8. Finally, go back to the board settings and change the Saved Filter to the newly created one

Team-Managed Projects

Based on missing official APIs we are not able to provide a project template feature for team-managed projects yet. Please watch & vote for the public feature request.

JSM Projects

We are evaluating our possibilities in providing a project template support for JSM projects. Please stay tuned and let our support know if you are waiting for this.

 

Project Specific Automation Rules

We would love to clone project specific automation rules as part of custom project templates.

Sadly there are no official APIs that allow cloning, creating, or even editing Jira’s automation rules. Please watch & vote the public feature requests.