Clone Pro Documentation
Complete guide to installing, configuring, and using Clone Pro for Jira Cloud. Clone entire projects with smart text replacement across all issues in one operation.
Overview
Clone Pro is a Jira Cloud app that enables cloning entire projects with smart text replacement capabilities. Unlike single-issue cloning tools, Clone Pro handles your complete project structure — epics, stories, tasks, and subtasks — while replacing text across all cloned content.
Key Features
- Full project cloning — Clone all issues from a source project to a new project
- Hierarchical tree view — See and select issues at any level (Epic → Story → Subtask)
- Smart text replacement — Define multiple find/replace pairs applied across all issues
- Selective cloning — Filter by issue type, status, or use presets
- Hierarchy preservation — Parent-child relationships are maintained
- Components & versions — Clone project metadata along with issues
- Progress tracking — Real-time progress indicator during cloning
- Runs on Atlassian — Built on Forge, 100% hosted on Atlassian infrastructure
🚧 Coming Soon: Clone Pro is currently in development and will be available on the Atlassian Marketplace soon.
Use Cases
Clone Pro is designed for teams with repeatable project structures:
- Agencies — Clone client onboarding project templates, replacing client names throughout
- Consulting firms — Duplicate engagement structures for each new client
- Compliance teams — Copy SOC2/audit projects for new cycles
- HR/Onboarding — Create employee onboarding projects from templates
- Quarterly planning — Duplicate sprint structures, replacing Q1 with Q2 everywhere
Installation
Clone Pro can be installed from the Atlassian Marketplace by a Jira administrator.
Requirements
- Jira Cloud (Software, Service Management, or Work Management)
- Jira administrator permissions to install apps
- Project administrator permissions to clone projects
Installation Steps
- Go to Jira Settings → Apps → Find new apps
- Search for "Clone Pro"
- Click Get app and follow the prompts
- Once installed, Clone Pro is accessible from the global navigation or project settings
Quick Start
Get started with Clone Pro in under 5 minutes:
- Open Clone Pro from the Apps menu or project settings
- Select your source project from the dropdown
- Review the issue tree — all issues are selected by default
- Add replacement pairs — e.g., find "Acme Industries" → replace with "New Client Ltd"
- Configure the target — enter new project name and key
- Click Clone and watch the progress
✓ Done! Your new project is created with all issues cloned and text replaced throughout.
Select Project
The first step is choosing which project to clone.
Project Selector
The project dropdown shows all Jira projects you have access to. You can:
- Type to filter the list
- See issue counts for each project
- Select any project regardless of type (Software, Business, Service Management)
Project Permissions
You must have at least "Browse Project" permission on the source project to clone it. To create a new target project, you need global project creation permissions.
Preview Contents
After selecting a project, Clone Pro loads and displays all issues in a hierarchical tree view.
Loading Issues
Clone Pro fetches all issues from the source project, including:
- All issue types (Epics, Stories, Tasks, Bugs, Subtasks, etc.)
- Parent-child relationships
- Epic-story links
- Issue metadata (status, priority, labels, etc.)
Performance note: Large projects (1000+ issues) may take a few seconds to load. Clone Pro uses pagination and rate limiting to handle projects of any size.
Issue Selection
The tree view lets you select exactly which issues to clone.
Tree View Controls
- Checkboxes — Click to select/deselect individual issues
- Expand/Collapse — Click the arrow to show/hide children
- Select parent — Automatically selects all children
- Deselect parent — Automatically deselects all children
Quick Actions
| Action | Description |
|---|---|
| Select All | Selects every issue in the project |
| Deselect All | Clears all selections |
| Expand All | Expands the entire tree |
| Collapse All | Collapses the tree to top level only |
Text Replacement
Define find/replace pairs to update text across all cloned issues.
Adding Replacement Pairs
Click "Add replacement pair" to add a new find → replace rule. You can add as many pairs as needed.
| Field | Description | Example |
|---|---|---|
| Find | The text to search for | Acme Industries |
| Replace with | The text to replace it with | New Client Ltd |
Replacement Options
- Case insensitive (default) — Matches "Acme", "ACME", "acme", etc.
- Case sensitive — Only matches the exact case you enter
- Whole word — Prevents partial matches (e.g., "Project" won't match "Projects")
Fields Affected
Text replacement is applied to:
- Summary
- Description (including rich text/ADF content)
- Comments
- Custom text fields
Note: Text inside attachments (Word docs, PDFs) is not modified. Only Jira field content is replaced.
Target Configuration
Configure where the cloned issues will be created.
New Project Settings
| Field | Description | Example |
|---|---|---|
| Project Name | The name for the new project | New Client Onboarding |
| Project Key | The unique key (2-10 uppercase letters) | NCO |
Project Key Rules
- Must be 2-10 characters
- Must be uppercase letters only
- Must be unique across your Jira instance
- Clone Pro validates the key before cloning
Tree View
The hierarchical tree view is the core of Clone Pro's interface.
Hierarchy Display
Issues are displayed in a parent-child hierarchy:
📁 Epic: Client Onboarding Framework
├── 📄 Story: Initial Setup
│ ├── 📋 Subtask: Configure workspace
│ └── 📋 Subtask: Set up credentials
├── 📄 Story: Data Migration
│ ├── 📋 Subtask: Export data
│ └── 📋 Subtask: Import data
└── 📄 Story: Training
Visual Indicators
- Icons — Issue type icons match your Jira configuration
- Status badges — Current issue status shown as colored badges
- Selection state — Checked, unchecked, or partially selected (for parents)
Filters & Presets
Quickly filter which issues to include in the clone.
Issue Type Filter
Show or hide issues by type:
- Epic
- Story
- Task
- Bug
- Subtask
- Custom issue types
Status Filter
Filter by issue status:
- To Do
- In Progress
- Done
- Custom statuses
Presets
| Preset | Description |
|---|---|
| Select All | Include every issue regardless of type or status |
| Open Work Only | Exclude Done/Completed issues |
| Structure Only | Only Epics and Stories (no subtasks) |
What Gets Cloned
Understanding exactly what Clone Pro copies to the new project.
Included
| Item | Details |
|---|---|
| Issues | All selected issues with full field values |
| Hierarchy | Parent-child and epic-story relationships |
| Custom fields | All custom field values are copied |
| Attachments | All files attached to issues |
| Comments | All comments with text replacement applied |
| Internal links | Links between issues within the project |
| Components | Project components are recreated |
| Versions | Project versions are recreated |
| Labels | All labels are copied to new issues |
Not Included
| Item | Reason |
|---|---|
| Cross-instance cloning | Requires Connect app architecture (future consideration) |
| Workflow post-functions | Project configuration, not issue data |
| External issue links | Links to issues outside the source project |
| Project settings | Schemes, permissions, workflows (new project uses defaults) |
| Worklogs | Time tracking data is not copied |
Progress Tracking
Clone Pro shows real-time progress during the cloning operation.
Progress Indicator
- Progress bar — Visual percentage complete
- Issue counter — "Cloning issue 45 of 120"
- Current issue — Shows the issue currently being processed
- Time estimate — Approximate time remaining
Completion Summary
When cloning completes, you'll see:
- Total issues cloned
- Total attachments copied
- Total comments cloned
- Any errors or warnings
- Link to the new project
Permissions
Clone Pro requires specific Jira permissions to function.
App Permissions
| Permission | Purpose |
|---|---|
read:jira-work |
Read issues, fields, comments, attachments |
write:jira-work |
Create issues, comments in target project |
manage:jira-project |
Create new projects, components, versions |
manage:jira-attachment |
Read and create attachments |
storage:app |
Store job progress and configuration |
User Permissions
- Source project — Browse Project permission required
- Target project — Create Issues permission (or project creation permission for new projects)
Privacy: Clone Pro runs entirely on Atlassian infrastructure. Your data never leaves Atlassian's servers, and the app qualifies for the "Runs on Atlassian" trust badge.
Limits & Performance
Clone Pro is designed to handle large projects efficiently.
Supported Project Sizes
| Project Size | Approximate Time |
|---|---|
| Small (< 100 issues) | Under 1 minute |
| Medium (100-500 issues) | 1-5 minutes |
| Large (500-2000 issues) | 5-20 minutes |
| Very large (2000+ issues) | 20+ minutes |
Rate Limiting
Clone Pro respects Atlassian's API rate limits by:
- Batching API requests
- Automatic backoff and retry on rate limit errors
- Parallel processing where safe
Async Processing
For large projects, cloning runs asynchronously. You can close the browser and return later — the job continues in the background.
Troubleshooting
Clone Pro doesn't appear in the menu
- Ensure the app is installed correctly (check with your Jira admin)
- Refresh the page and try again
- Check that you have the required permissions
Project selector is empty
- Verify you have Browse Project permission on at least one project
- Check that your Jira instance has projects (not just a blank instance)
Text replacement isn't working
- Check that your search text matches exactly (including spaces)
- Verify case sensitivity settings match your text
- Ensure the text exists in supported fields (summary, description, comments)
Cloning is slow
- Large projects naturally take longer — this is expected
- Many attachments increase cloning time significantly
- Network conditions between you and Atlassian may affect speed
Some issues weren't cloned
- Check the completion summary for any errors
- Verify you selected those issues in the tree view
- Ensure you have permission to view those issues
Frequently Asked Questions
Can I clone to an existing project?
Not in the initial release. Clone Pro creates a new project for each clone operation. Cloning to existing projects is planned for v2.
Can I save replacement templates for reuse?
Saved templates are planned for v2. Currently, you'll need to enter replacement pairs each time.
Will it replace text inside attachments?
Not in the initial release. Attachment content replacement (Word, Excel) is planned for v2.
How does Clone Pro differ from Clone & Replace?
Clone & Replace is for single-issue cloning. Clone Pro handles entire projects — hundreds or thousands of issues at once.
Can I clone across Jira instances?
No. Cross-instance cloning requires a Connect app architecture which is significantly more complex. Clone Pro works within a single Jira Cloud instance.
What happens if cloning fails partway through?
Clone Pro creates a partial project with the issues that were successfully cloned. You can view the error details and retry or delete the partial project.
Is my data secure?
Yes. Clone Pro is built on Atlassian Forge and runs 100% on Atlassian's infrastructure. Your data never leaves Atlassian's servers.
What happens to the original project?
The original project is not modified in any way. Clone Pro only reads from the source and creates a new target project.