Cloning an existing Program
The cloning feature replicates all tasks and relations between them, while following the same synchronization and scope definitions.
Even though Cloning can be a very powerful functionality, it will not replace Program Creation functionality. As it copies Programs only on their highest layer, it is very useful for the purpose of creating Project Portfolio Templates, which we can later re-use for certain types of Programs.
Feature | Description |
|---|---|
Clone an existing Program | Pick a Program to be cloned. |
Basic data | Enter the following information:
Select an existing project where the cloned issues will be created. Click the "Let's get it started!' button. |
Which data can be cloned?
The most common cases and limitation are described in the table below:
| Data | Cloning result (Yes / No) |
|---|---|
| Jira issue | Yes. The cloned issues can be linked using a link type selected in Global configuration - Gantt configuration. By default it is a 'Clone' link. |
| Task structure | Yes. |
| Issue types | Partially. If the project does have the required issue types in the issue type scheme. If a new project with different issue types (issue scheme) is used the default issue type will be used for all tasks which can not be matched. Epics and sub-tasks will be cloned as default issue types. |
| Summary field | Yes. |
| Start / End date synchronized fields | Yes. The fields selected as Start / End date in Global configuration - Task configuration. |
| Other fields beside Summary and synchronized date fields | No. |
| Required fields | No. The required fields can not be populated by the app, hence before cloning the Program make sure all possible fields are set as optional |
| Version or Component | No. The app is capable of creating Jira Issues and recreating the structure. It is not capable of creating anything that is not a Jira Issue while cloning, therefore it will automatically replace the original Version or Component with an Artificial Task. |
