Versions Compared

Version Old Version 15 New Version 16
Changes made by

Litew8 GmbH

Litew8 GmbH

Saved on

Key

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

...

Info

Status
colourBlue
titleExperimental

  • Limitation: Only the first 500 issues of the filter will be cloned.

  • Limitation: Sub-tasks will be ignored during the cloning process.

  • Ignored Fields: The following fields will be ignored during the cloning process: Attachment, Issue links, Parent, Epic Link, Sprint, Rank, Versions, Components.

We acknowledge these limitations and apologize for any inconvenience they may cause. Rest assured, we are actively working to address these restrictions one at a time, aiming to enhance the feature and provide a smoother experience for our users.

  1. Specify a JQL filter of issues you want to clone. Saving the JQL filter will validate the filter and potentially return an error message

  2. Specify who should be the reporter of the cloned issues.
    Options:

    1. Keep existing

    2. Project lead

    3. Project creator

    4. Technical app user

    5. Custom user.

  3. Specify what to do with existing Epic links, or links to higher level hierachy (Jira premium)
    Options:

    1. Link to cloned Epic (default)

    2. Keep original Epic link

    3. Clear

Please note that only issue types configured in the template's issue type scheme will be cloned. Ensure that the desired issue types are properly set up in the template to enable their cloning during project creation.

...

.

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.

...