Video Tutorial

Watch this comprehensive video guide to learn how to use ProjectClone effectively:

Video Contents

This tutorial covers accessing ProjectClone, basic cloning workflow, scheme configuration, and troubleshooting common issues. Duration: approximately 5-10 minutes.

Accessing ProjectClone

ProjectClone is integrated directly into Jira's project interface. Here's how to access it:

1

Navigate to Source Project

Go to the project you want to clone. You need at least Project Administrator permissions or be granted specific ProjectClone access.

2

Access Project Settings

In the project sidebar, click "Project settings" at the bottom of the navigation menu.

3

Find ProjectClone Menu

In the project settings sidebar, look for the "ProjectClone" section. Click on "Clone Project" to begin.

Permission Requirements

If you don't see the ProjectClone option, contact your Jira administrator to request access. Only authorized users can clone projects for security reasons.

User Interface Overview

The ProjectClone interface is designed for simplicity and power. Here are the main sections:

Source Project Info

Displays details about the project you're cloning, including schemes and configurations.

New Project Details

Configure the name, key, and basic settings for your new project.

Scheme Selection

Choose which configurations to copy or replace with existing schemes.

User & Role Management

Configure project roles and user assignments for the new project.

Navigation Tips

  • Save Progress: Your configuration is automatically saved as you make changes
  • Validation: Real-time validation prevents configuration errors
  • Preview: Review all settings before executing the clone
  • Help Context: Hover over any field for detailed explanations

Basic Cloning Process

Follow this step-by-step process for standard project cloning:

1

Project Information

Enter the basic details for your new project:

Required Fields
Project Name: [Descriptive name for the project]
Project Key: [3-10 character unique identifier]
Project Lead: [User who will lead the project]
Description: [Optional project description]
Project Key Requirements

Project keys must be unique across your Jira instance and can only contain uppercase letters and numbers. Once set, they cannot be changed.

2

Scheme Configuration

For each scheme type, choose your preferred option:

  • Copy from source: Creates an exact duplicate of the source scheme
  • Use existing: Applies an existing scheme from your Jira instance
  • Use default: Applies the system default scheme

Available Schemes:

Workflow Scheme

Controls issue transitions and status flow

Permission Scheme

Manages who can view and edit issues

Notification Scheme

Defines when and who receives notifications

Issue Type Scheme

Determines available issue types

Field Configuration

Controls field visibility and requirements

Issue Security Scheme

Manages issue-level security restrictions

3

Components & Versions

Choose what to include from the source project:

  • Copy Components: Include project components with their leads and descriptions
  • Copy Versions: Transfer project versions and release information
  • Copy Project Roles: Maintain custom project roles and assignments
4

Review & Execute

Review your configuration in the summary panel, then click "Clone Project" to begin the process.

Clone Time

Most projects clone in 30 seconds to 2 minutes. Complex projects with many schemes may take longer.

Advanced Options

ProjectClone offers several advanced features for power users:

Bulk User Assignment

Efficiently manage user permissions during cloning:

  • Group-based Assignment: Assign entire user groups to project roles
  • CSV Import: Import user lists from spreadsheets
  • Template Roles: Apply predefined role templates
  • Permission Validation: Automatic validation of user permissions

Custom Scheme Handling

Advanced scheme management options:

Scheme Naming Convention
Copied Scheme Name Format:
"[Original Name] - [New Project Key]"

Example:
"Software Development Workflow - PROJ"

Selective Component Cloning

Choose specific components to clone rather than copying all:

1

Component Selection

In the components section, uncheck any components you don't want to include in the new project.

2

Lead Assignment

Modify component leads during the cloning process or keep the original assignments.

Monitoring Progress

Track your cloning operations and view detailed progress information:

Real-time Progress

View live updates as each component is cloned with percentage completion.

Operation History

Review past cloning operations with detailed logs and timestamps.

Error Reporting

Detailed error messages and suggested resolutions for any issues.

Progress Phases

1

Validation

ProjectClone validates all settings and checks for conflicts or issues.

2

Project Creation

The base project structure is created with the specified name and key.

3

Scheme Application

Workflows, permissions, and other schemes are applied to the new project.

4

Final Configuration

Components, versions, and user roles are configured and assigned.

Common Issues & Solutions

Here are solutions to frequently encountered problems:

Permission Issues

Problem: "Access Denied" Error

Solution: Contact your Jira administrator to grant ProjectClone permissions. You need either Project Admin access or specific ProjectClone user permissions.

Project Key Conflicts

Problem: "Project Key Already Exists"

Solution: Project keys must be unique. Try a variation like adding numbers or abbreviations. Example: PROJ becomes PROJ2 or PROJ-DEV.

Scheme Conflicts

Problem: Scheme Name Conflicts

Solution: When copying schemes, ProjectClone automatically appends the project key to avoid conflicts. Original names are preserved in the description.

Performance Issues

  • Large Projects: Projects with many components may take longer to clone
  • Network Issues: Slow internet can affect cloning speed
  • Concurrent Operations: Multiple simultaneous clones may slow performance
  • Peak Hours: Jira system load can impact cloning speed
Best Practices

For optimal performance, clone projects during off-peak hours and avoid running multiple cloning operations simultaneously. Always test with smaller projects first.