Frequently Asked Questions
Find quick answers to common questions about ProjectClone installation, usage, troubleshooting, and best practices.
FAQ Categories
Getting Started
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.
Installation & Licensing
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.
Usage & Operations
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.
Troubleshooting
Solution: This usually means you don't have the necessary permissions. Contact your Jira administrator to grant you ProjectClone access, or ensure you have Project Administrator permissions for the project you want to clone.
Solution: Check the error message for specific details. Common issues include permission problems, invalid project keys, or network timeouts. Try the operation again, and if it continues to fail, contact support with the error details.
Solution: This can happen if you don't have permission to view all components in the source project, or if some components were deselected during the cloning process. Check your permissions and review the clone configuration.
Solution: ProjectClone copies role structures but users must exist in your Jira instance to be assigned to roles. If users were deactivated or removed, they won't appear in the cloned project. Re-add users manually if needed.
Solution: Very complex projects with many schemes and components can take longer. If it's been over 5 minutes, there may be an issue. Check your network connection and Jira system performance. Contact support if the operation appears stuck.
Solution: When copying schemes, ProjectClone automatically appends the project key to avoid naming conflicts. If you're still seeing conflicts, choose to use existing schemes instead of copying, or manually rename conflicting schemes before cloning.
Security & Compliance
Yes, ProjectClone runs entirely within Atlassian's secure Forge infrastructure. No data leaves your Jira instance, and all processing occurs server-side with enterprise-grade security.
ProjectClone inherits Atlassian's compliance certifications including SOC 2 Type II, ISO 27001, GDPR compliance, and Privacy Shield framework adherence. See our Security & Compliance page for complete details.
ProjectClone only accesses project configuration data (schemes, settings, roles) necessary for cloning. It does NOT access issue content, comments, attachments, or store any data permanently. All processing is transient.
Yes, ProjectClone is suitable for regulated industries. It inherits Atlassian's compliance with regulations like HIPAA, SOX, and others. Review our Security & Compliance documentation and consult with your compliance team.
Yes, all ProjectClone operations are logged including who performed the action, when, what was cloned, and the result. Audit logs can be exported for compliance reporting.
Technical Questions
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.
If you can't find the answer to your question here, check our other documentation pages or contact our support team. We're here to help you get the most out of ProjectClone!