Documentation User Guide Project Cloning
Install App

Advanced Project Cloning

Master advanced cloning techniques, scheme management strategies, and optimization methods for complex project structures.

20 min read Updated: January 2025 Advanced Users

Advanced Topics

Cloning Strategies

Different scenarios require different approaches to project cloning. Here are proven strategies for various use cases:

Template-Based Cloning

Create standardized project templates for consistent organizational structure:

1

Create Master Template

Set up a "template" project with your organization's standard workflows, permissions, and configurations. Don't use this project for actual work.

Template Project Example 
Project Name: "Development Team Template"
Project Key: DEVTEMPL
Purpose: Master template for all development projects
Components: Frontend, Backend, QA, DevOps
Workflows: Custom development workflow
Permissions: Standard team permission scheme
2

Standardize Schemes

Configure all schemes (workflow, permission, notification) to reflect your organization's best practices.

3

Clone from Template

Use your template project as the source for all new projects, ensuring consistency across your organization.

Environment Migration

Move projects between Jira instances or environments:

Dev to Staging

Clone development projects to staging environments for testing

Staging to Production

Promote tested configurations to production environments

Backup Projects

Create backup copies before major configuration changes

Cross-Instance Limitations

ProjectClone works within a single Jira Cloud instance. For cross-instance migrations, use ProjectClone to standardize configurations, then recreate in the target instance.

Advanced Scheme Management

Master the complexities of Jira scheme management for optimal project cloning:

Scheme Dependency Mapping

Understanding how schemes interact prevents cloning issues:

Scheme Dependencies 
Workflow Scheme
├── Issue Type Scheme (defines available issue types)
├── Field Configuration Scheme (controls field behavior)
└── Screen Scheme (defines issue screens)

Permission Scheme
├── Project Role Scheme (defines available roles)
└── Issue Security Scheme (optional, for sensitive issues)

Notification Scheme
└── Project Role Scheme (defines who gets notifications)

Scheme Reuse vs. Cloning

Decide when to reuse existing schemes versus creating new ones:

Reuse Existing

When: Standard configurations, shared teams, similar workflows

Benefits: Consistency, easier maintenance, shared updates

Clone Schemes

When: Custom requirements, independent evolution, isolated changes

Benefits: Independence, customization, no cross-project impact

Scheme Naming Conventions

1

Organizational Standards

Establish consistent naming patterns:

Naming Examples 
Format: [Department]-[Project Type]-[Scheme Type]
Examples:
- "Engineering-Development-Workflow"
- "Marketing-Campaign-Permission"  
- "Support-Ticket-Notification"

Cloned schemes auto-append project key:
- "Engineering-Development-Workflow-PROJ1"

Complex Configuration Scenarios

Handle advanced project structures and requirements:

Multi-Team Projects

Configure projects for multiple teams with different access levels:

1

Component-Based Separation

Use components to separate team responsibilities:

  • Frontend Component: UI/UX team with frontend developers
  • Backend Component: API developers and architects
  • QA Component: Testing team with different permissions
  • DevOps Component: Infrastructure and deployment team
2

Role-Based Permissions

Configure custom project roles for each team:

Custom Roles 
Frontend Developers:
- Create/Edit issues in Frontend component
- View all components, edit own

Backend Developers:  
- Create/Edit issues in Backend component
- View all components except sensitive QA data

QA Engineers:
- Create/Edit issues in any component
- Transition issues through testing states
- Access to all project data

Hierarchical Project Structures

Create parent-child project relationships:

Program Management

Parent project for program oversight, child projects for individual teams

Product Lines

Separate projects for each product with shared configurations

Client Projects

Template-based projects for different clients with customizations

Bulk Operations

Efficiently manage multiple projects and large-scale cloning operations:

Sequential Cloning

Plan and execute multiple project clones systematically:

1

Planning Phase

Document your cloning strategy before beginning:

Cloning Plan Template 
Source Project: TEMPLATE
Target Projects:
1. DEV-TEAM-1 (Development Team Alpha)
2. DEV-TEAM-2 (Development Team Beta)  
3. QA-ENV (QA Environment)
4. STAGING (Staging Environment)

Scheme Strategy:
- Workflow: Clone for DEV teams, reuse existing for QA/Staging
- Permissions: Customize per team
- Components: Standard set for all projects
2

Execution Strategy

Clone projects in logical order to avoid dependency issues:

  • Infrastructure First: Base/shared projects before dependent ones
  • Team Separation: One project per team to avoid conflicts
  • Validation Breaks: Test each clone before proceeding
  • Documentation: Record configurations for troubleshooting

Batch User Management

Efficiently assign users across multiple projects:

User Assignment Strategy

Create user groups in Jira administration, then assign entire groups to project roles. This makes bulk management much easier than individual user assignments.

Performance Optimization

Optimize cloning operations for speed and reliability:

Project Size Considerations

Small Projects

< 10 components: 30-60 seconds
Minimal optimization needed

Medium Projects

10-50 components: 1-3 minutes
Consider selective cloning

Large Projects

> 50 components: 3+ minutes
Optimize timing and approach

Optimization Techniques

  • Off-Peak Timing: Clone during low-traffic hours for better performance
  • Selective Components: Only clone necessary components to reduce processing
  • Scheme Reuse: Reuse existing schemes instead of cloning when possible
  • Staged Approach: Clone base project first, then add complexity
  • Monitor Resources: Watch Jira system performance during operations
Performance Impact

Large cloning operations can impact Jira performance. Schedule intensive operations during maintenance windows or low-usage periods.

Automation & Templates

Streamline repetitive cloning tasks with automation strategies:

Template Libraries

Build a library of template projects for different scenarios:

1

Create Template Categories

Template Organization 
Software Development Templates:
├── AGILE-TEMPLATE (Scrum/Kanban workflows)
├── DEVOPS-TEMPLATE (CI/CD focused)
└── MOBILE-TEMPLATE (Mobile app development)

Business Templates:
├── MARKETING-TEMPLATE (Campaign management)
├── HR-TEMPLATE (Hiring and onboarding)
└── FINANCE-TEMPLATE (Budget and reporting)

Support Templates:
├── HELPDESK-TEMPLATE (Customer support)
└── INTERNAL-TEMPLATE (IT support)
2

Documentation Standards

Document each template's purpose and configuration:

  • Template Purpose: What type of projects this serves
  • Included Schemes: Which workflows and permissions are configured
  • User Roles: Standard team structure and permissions
  • Components: Default project components and their purpose
  • Customization Points: Areas typically modified for new projects

Standardization Best Practices

Template Maintenance

Regularly review and update your template projects to incorporate lessons learned and organizational changes. Assign template ownership to ensure they stay current.

Integration Opportunities

Consider integrating ProjectClone workflows with other tools:

Jira Automation

Use Jira's automation rules to trigger follow-up actions after cloning

Development Tools

Coordinate project cloning with repository creation and CI/CD setup

Reporting Tools

Include new projects in dashboards and reporting automatically