2.6 Issues: Clone & Predefine


Kickstart projects with a set of predefined or cloned Epics, Tasks & Sub-Tasks.

Project & Issue Templates for Jira allows to automatically create issues with every created project/target 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

  1. 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 & Issue Templates for Jira supports to clone up to 700 issue with each template usage.

  • 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.

  1. In the ‘Issues’ tab of template settings, click on the edit icon of ‘Issue source project / JQL filter’

  2. 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 query. Select ‘Custom Jira query(JQL)’ and specify the JQL filter. Click ‘Save' to confirm, this will validate the filter and potentially return an error message with hints.

    Option 3: Clone all issues from an existing JQL filter. Select ‘Source filter’. You can select the existing JQL filter in a dropdown
    Click ‘Save’ to confirm

  3. A refreshable counter will display the amount off issues that exist inside the selected source project or specified JQL filter.

  4. Specify additional configuration regarding issue cloning

  1. Keep existing reporter (default)

  2. Project lead

  3. Project creator

  4. Technical app user

  5. Placeholder
    (Select user picker placeholder)

  6. Custom user

  1. Link to cloned Epic (default)

  2. Keep original Epic link

  3. Clear

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.

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

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.

  1. Click on ‘Predefine custom issue’ to create a new predefined issue.

  2. 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.

Instead of creating predefined issues from scratch, it is possible to clone existing predefined issues.