Project Cloner Documentation
Project Cloner lets you clone an entire Jira project's configuration from one Atlassian Cloud site to another — in minutes, not days. It's available on the Atlassian Marketplace.
Why Project Cloner?
- Save hours of manual setup — Stop re-creating workflows, screens, and fields by hand every time you spin up a new project.
- Cross-site cloning — Clone from any Jira Cloud site to any other site in your Atlassian organization.
- Full fidelity — 13 configuration categories are systematically replicated so your new project is production-ready immediately.
- Real-time progress — Watch each step complete live. Get a detailed report at the end.
Installation
- Go to the Project Cloner listing on the Atlassian Marketplace.
- Click "Get it now" (or "Try it free" if a trial is available).
- Select the Jira Cloud site where you want to install the app.
- Review and approve the permissions.
- Once installed, Project Cloner appears in your Jira top navigation under Apps → Project Cloner.
Initial Setup
After installation, a Jira admin needs to set up the service account credentials. This is a one-time setup that takes about 2 minutes.
Step 1: Create a Service Account
Project Cloner needs an Atlassian Organization Service Account to read configuration from source sites and write to the destination. If your organization doesn't have one yet:
- Go to admin.atlassian.com.
- Navigate to Settings → API Keys (or Service Accounts).
- Create a new service account and generate OAuth 2.0 credentials.
- Save the Client ID and Client Secret securely.
Step 2: Enter Credentials in the App
- In Jira, go to Apps → Project Cloner Settings (admin page).
- Enter the Client ID and Client Secret.
- Click "Save Credentials".
- The app will validate the credentials and show a green status indicator.
Cloning a Project
Once setup is complete, any authorized user can clone projects:
Step 1: Open the Clone Wizard
Go to Apps → Project Cloner in the Jira top navigation.
Step 2: Select the Source
The wizard displays all Jira Cloud sites in your organization. Select a site, then choose the project you want to clone from.
Step 3: Configure the New Project
Enter the details for the destination project:
- Project Name — The display name (e.g., "Customer Portal")
- Project Key — A unique 2–10 character key (e.g., "CP"). The app validates this in real-time.
- Description — Optional project description
Step 4: Click "Provision" and Watch
The 13-step provisioning process runs automatically. You'll see real-time progress for each step with ✓ success, ⏭ skipped, or ⚠ warning indicators.
Step 5: Review the Report
When done, you'll see a summary report. Your new project is immediately available in Jira — fully configured and ready for your team.
What Gets Cloned
Project Cloner replicates 13 categories of project configuration:
| # | What | Details |
|---|---|---|
| 1 | Project | Created with correct type (Software, Service Desk, or Business) and template |
| 2 | Issue Types | Bug, Story, Task, etc. — matched or created as needed |
| 3 | Issue Type Scheme | Configured with the right types and default |
| 4 | Workflows | All statuses, transitions, and status categories |
| 5 | Workflow Scheme | Issue type → workflow mappings |
| 6 | Permission Scheme | Matched by name on the destination site |
| 7 | Screens & Custom Fields | Screens, tabs, field layouts, and custom field option lists |
| 8 | Field Configurations | Hidden/required settings per issue type |
| 9 | Components | Names, descriptions, and assignee settings |
| 10 | Filters | JQL automatically remapped to the new project key |
| 11 | Boards | Scrum, Kanban, or Simple boards with proper filters |
| 12 | Dashboards | Including gadgets and sharing permissions |
| 13 | Report | Detailed status for every step |
Reading the Report
After provisioning, each of the 13 steps shows one of three statuses:
- ✓ Success — Configuration was cloned successfully.
- ⏭ Skipped — The source project didn't have this configuration (e.g., no components). This is normal.
- ⚠ Warning — The step completed with minor issues (e.g., one custom field couldn't be created because it requires a third-party plugin). Details are shown in the step description.
You can view past provisioning reports at any time from the Job History section in the app.
Managing Credentials
The admin settings page (Apps → Project Cloner Settings) lets Jira admins:
- Check token health — Verify the service account is connected and working
- Update credentials — Change the Client ID or Client Secret if rotated
- Remove credentials — Delete stored credentials if uninstalling
Permissions
Project Cloner requires the following Jira permissions:
| Permission | Why |
|---|---|
| Read project data | To extract configuration from the source project |
| Create & configure projects | To create the new project and set up schemes |
| Manage workflows & screens | To create workflows, screens, and field configurations |
| Read user info | To resolve the project lead's account |
Only Jira administrators can install the app and configure service account credentials. Regular users can use the clone wizard if granted access.
Troubleshooting
"Projects can only be cloned into the site where Project Cloner is installed"
The app must be installed on the destination site. If you want to clone into a different site, install Project Cloner on that site first.
A custom field wasn't created
Some custom field types require specific Jira apps or plugins. If the source project uses a custom field from a third-party app, that app must also be installed on the destination site.
Token health check fails
Go to Apps → Project Cloner Settings and verify:
- The Client ID and Client Secret are correct
- The service account hasn't been deactivated in your Atlassian admin console
- The secret hasn't been rotated — if it was, enter the new one
Provisioning completed with warnings
Warnings are non-fatal. The project was created successfully, but some minor configuration elements couldn't be cloned (e.g., a custom field type isn't available). Review the warning details in the report and manually configure those items if needed.
Need help?
If you run into an issue not covered here, please contact our support team with your provisioning report details.
Frequently Asked Questions
Does Project Cloner copy issues?
No. It clones project configuration only — workflows, screens, fields, schemes, boards, dashboards, and components. Issues and their data remain on the source site.
Can I clone between different organizations?
No. Both the source and destination sites must be in the same Atlassian organization. The service account authenticates within a single org.
Will it affect my existing projects?
No. Project Cloner creates new resources (schemes, workflows, etc.) for the destination project. It never modifies or deletes existing configuration on either site.
Is it safe to use on production sites?
Yes. The app only creates new resources and assigns them to the new project. No existing configuration is changed. We recommend testing on a staging site first, but it's safe for production use.
What project types are supported?
Software projects (Scrum and Kanban), Service Desk projects, and Business projects are all supported.
How long does cloning take?
Most projects clone in under 5 minutes. Complex projects with many custom fields and workflows may take longer, but the process has a 15-minute timeout.
How does billing work?
Project Cloner is billed through the Atlassian Marketplace. Check the listing page for current pricing and trial options.