Important note Retirement of icTime and Retirement of biz on December 29th, 2023
Copy Project (GUI)
The functionality to copy a project is not only offered via the REST API, but is also added as a navigation item to the JIRA project navigation as a convencience features for administrators.
Copy Project
The respective item appears in the JIRA project dropdown if a user has the global "JIRA Administrators" permission.
If a user has this JIRA permission, the user will be able to create projects. There might be other permissions required (e.g. create issue).
If certain permissions are missing (e.g. create issues), the project might be created/copied, but e.g. the issues are not copied.
Copy Settings
When copying, you have the enter the following information resp. can use the following options:
| Field | Description | Remarks |
|---|---|---|
| Source Project Key | Key of the project you want to copy/use as template. | mandatory |
| Target Project Key | (Unique) key of the new project. | mandatory |
| Target Project Name | (Unique) name of the new project. | mandatory |
| Copy Versions | If checked, versions are copied, too. | |
| Copy Components | If checked, components are copied, too. | |
| Copy Issues | If checked, issues are copied, too. | Issues are copied with attachments and with sub-tasks, but without
Issues will always be created in status "Open", the original status is not copied. To copy issue, you have to copy components and versions, too! |
The following elements/relations of a JIRA project are always copied and can't be configured:
- Project description and avatar, if applicable
- Permission Scheme
- Notification Scheme
- Issue Type Scheme
- Workflow Scheme
- Screen Scheme
- Field Configuration Scheme
- Role Configuration