Versions Compared

Version Old Version 34 New Version Current
Changes made by

Wolfgang Diehl

Wolfgang Diehl

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Table of Contents
minLevel1
maxLevel6
outlinefalse
typelist
printablefalse

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.

Info

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

...

2. In the template settings modal, click on the tab ‘Issues’

...

Clone existing issues

Info

Status
colourBlue
titleNotes

  • 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 500700 issue with each new projecttemplate usage.

  • The following fields will be ignored during the cloning process: Attachment, Issue links, Sprint, Rank.

  • Issue cloning and linking occasionally fails if the issue summary uses special characters like parentheseslinks, 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 ‘Source JQL filterCustom 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.

    image-20240614-115455.pngImage Added

    Option 3: Clone all issues from an existing JQL filter. Select ‘Source filter’.

    Image Removed

    You can select the existing JQL filter in a dropdown
    Click ‘Save’ to confirm

    image-20240614-115422.pngImage Added

  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

Expand
titleSpecify who should be the reporter of the cloned issues.

  1. Keep existing reporter (default)

  2. Project lead

  3. Project creator

  4. Technical app user

  5. Placeholder
    (Select user picker placeholder)

  6. Custom user

Expand
titleSpecify what to do with existing Epic links, or links to higher level hierarchy (Jira premium)

  1. Link to cloned Epic (default)

  2. Keep original Epic link

  3. Clear

Expand
titleSpecify how to handle issue links.
Info

Issue linking can only be set once all issues are cloned. To avoid delays and API-limitations, issue linking happens in the background ~5-10 ~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.

Expand
titleSpecify how to handle issue status.

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

Info

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/target 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.

...