...
Info |
---|
Issue Creation - App Permission PrerequisiteProject role: atlassian-addons-project-access requires the following ‘Project permission’ on projects involved:
|
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 ‘Clone & predefine issues’
...
Clone existing issues
...
Info | ||||||
---|---|---|---|---|---|---|
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. |
...
In the ‘Issues’ tab of template settings, click on the edit icon of ‘Issue source project / JQL filter’
Option A: 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 B: 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.
Specify who should be the reporter of the cloned issues.
Options:Keep existing reporter (default)
Project lead
Project creator
Technical app user
Custom user.
Specify what to do with existing Epic links, or links to higher level hierarchy (Jira premium)
Options:Link to cloned Epic (default)
Keep original Epic link
Clear
...
Info |
---|
Note: 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.
...