Kickstart each new project with a set of predefined Epics, Tasks & Sub-Tasks. Project Templates for Jira allows to automatically create issues with every created project. To do that admins can either specify a JQL filter of existing issues, or predefine a set of new issues.
Issue Creation - App Permission Prerequisite
Project role: atlassian-addons-project-access requires the following ‘Project permission’ on projects involved:
View Projects, View Issues, Create Issues, Assign Issues, Modify Reporter
To setup issue cloning or predefine issues, click either on ‘2. Configure template settings' in the dialog or on the settings icon in under Actions.
2. In the template settings modal, click on the tab ‘Issues’
Clone existing issues
NOTES
Only issue types configured in the template’s issue type scheme will be cloned.
New templates will NOT clone any issues unless admins configure it in the template settings.
Project Templates for Jira supports to clone up to 500 issue with each new project.
The following fields will be ignored during the cloning process: Attachment, Sprint, Rank.
Issue links, Remote issue links, Weblinks and confluence page links will be maintained after a delay of ~1-2min to avoid API rate limits.
In the ‘Issues’ tab of template settings, click on the edit icon of ‘Issue source project / JQL filter’
Choose how to select issue source
Option 1: Clone all issues from a source project. Select ‘Source project’ and select the project you want to clone issues from. Click ‘Save’ to confirm.
Option 2: Clone all issues from a JQL filter. Select ‘Source JQL filter’ and specify the JQL filter. Click ‘Save' to confirm, this will validate the filter and potentially return an error message with hints.
A refreshable counter will display the amount off issues that exist inside the selected source project or specified JQL filter.
Specify additional configuration regarding issue cloning
Issue linking can only be set once all issues are cloned. To avoid delays and API-limitations, issue linking happens in the background ~10 seconds after project creation.
Option 1: Link to cloned issues (default)
Issue links where both linked issues are cloned are will be set between the cloned issues.
Option 2: Keep original issue link targets
Issue links will be created between the cloned issue and the original issue link target outside the created project.
Option 3: Clear
Cloned issues will be created without issue links.
Option 1: Use first status of new workflow. (default)
Example: Cloned list of tasks that should always start at the beginning of the workflow regardless if they are resolved in the source project.
Option 2: Maintain original status
Issue status can only be maintained if the following requirements are fulfilled. Otherwise the first status of the new workflow is selected.
Status needs to be present in the workflow that the issue type is associated with in the new project.
Status needs to be directly reachable from the first status of the workflow via direct or global transition.
The transition reaching the status is not allowed to have blocking Validators or Conditions.
Predefine new issues
Additionally to cloning issues, Project Templates for Jira allows to predefine new issues in the template settings. You can specify a hierarchy Epic → Task/Story → Sub-task to link predefined issues together.
Click on ‘Predefine custom issue’ to create a new predefined issue.
Specify predefined issue fields and click ‘Create’
3. Result: Each project created based on ‘My first project template’ will now also create a Task called ‘Check project role assignment’. You can click Edit or Trash icon to adjust existing predefined issues.
If you need predefined issues with custom field values, use the clone issue functionality instead or connect Project Templates for Jira with Jira automation to create advanced automation.
Instead of creating predefined issues from scratch, it is possible to clone existing predefined issues.
