Frequently Asked Questions

ProjectClone is a Jira app built on the Atlassian Forge platform that allows you to clone entire Jira projects with all their configurations, schemes, components, and user roles intact. It's perfect for creating project templates, migrating environments, or standardizing project structures.

Unlike Jira's basic templates, ProjectClone copies complete project configurations including custom workflows, permission schemes, field configurations, components with leads, project roles, and user assignments. It creates an exact replica of your source project rather than a basic template structure.

Yes, you need either Jira Administrator permissions or specific ProjectClone permissions granted by your administrator. At minimum, you must have Project Administrator access to the projects you want to clone.

Most projects clone in 30 seconds to 2 minutes depending on complexity. Simple projects with few components clone faster, while complex projects with many schemes and components may take longer.

Install ProjectClone from the Atlassian Marketplace. Go to Settings → Apps → Find new apps, search for "ProjectClone", and click "Get it now". Installation takes 2-3 minutes and requires Jira Administrator permissions.

Yes, ProjectClone offers a free trial period through the Atlassian Marketplace. Check the marketplace listing for current trial duration and terms.

ProjectClone is built for Jira Cloud and works with all current Jira Cloud instances. It's built on the Forge platform and doesn't support Jira Server or Data Center.

ProjectClone is licensed based on the number of Jira users in your instance. Pricing follows Atlassian's standard app licensing model with tiers for different user counts.

Each Jira Cloud instance requires a separate ProjectClone license. ProjectClone works within a single Jira instance and cannot clone projects between different instances.

ProjectClone copies project metadata, workflow schemes, permission schemes, issue type schemes, field configurations, notification schemes, components, versions, project roles, and user assignments. It does NOT copy issues, comments, attachments, or issue content.

Yes! For each scheme type, you can choose to copy from the source project, use an existing scheme, or apply the system default. This gives you flexibility to customize the cloned project's configuration.

Project keys must be unique. If you enter a key that already exists, ProjectClone will display an error and prevent the clone operation. Choose a different, unique project key.

Currently, ProjectClone processes one project at a time. You can start multiple cloning operations sequentially, but they will be processed one after another for optimal performance.

Absolutely! Once cloned, the new project is completely independent. You can modify any configurations, add/remove users, change workflows, or customize it however you need without affecting the source project.

Custom fields that are configured in the source project's field configuration will be available in the cloned project with the same settings. However, custom field data/values from issues are not copied since issues themselves aren't cloned.

ProjectClone carries the Runs on Atlassian trust signal on Marketplace. Review the listing, partner privacy policy, and app permissions as part of your security assessment.

ProjectClone does not claim independent SOC 2 or ISO 27001 certification. Atlassian platform certifications do not automatically certify ProjectClone. See the Security & Privacy page for the scope of our published information.

Review the app permissions and partner privacy policy linked from Marketplace. Contact support for version-specific details about data processing, storage, retention, and deletion.

Your organization should assess ProjectClone against its own requirements before using it with regulated data. Platform hosting alone does not establish app compliance. Contact support for information needed for your review.

Contact support to confirm which operation records are available for your installed version. This documentation does not promise a complete audit trail, audit-log export, or a fixed retention period.

There's no specific size limit, but very large projects (100+ components, complex workflows) will take longer to clone. Most projects clone successfully regardless of size, though performance may vary with complexity.

ProjectClone clones standard Jira configurations. Custom configurations from third-party apps may or may not be preserved depending on how they're implemented. Test with a sample project first if you use many third-party apps.

ProjectClone currently operates through the Jira web interface. For automation needs, consider using Jira's automation rules to trigger follow-up actions after project cloning is completed.

ProjectClone focuses on core Jira configurations (workflows, permissions, fields). App-specific configurations from other Marketplace apps may need to be reconfigured manually in the cloned project.

ProjectClone creates independent projects. Any project dependencies or links to other projects are not automatically recreated - you'll need to establish these relationships manually in the cloned project if needed.