Approve every expected difference
See what copies, transforms, or stays behind before creating Jira targets.
APPROVAL-BOUND CLONING FOR JIRA CLOUD
Clone Jira work
without crossing your fingers.
CloneGuard checks what will move before anything is created, stops when the approved conditions change, and reads every result back from Jira.
- Runs on Atlassian
- Same-site Jira Cloud
- Zero source writes
EXPLAINED LIKE YOU’RE FIVE
Think of it as a moving checklist with a seal.
Before a moving truck leaves, you write down every box, agree what stays behind, and seal the list. If the destination rules change on the way, the truck stops. At the end, somebody checks every delivered box against the list. CloneGuard does that for Jira work items.
ONE CONTROLLED JOB
Four moves from “copy” to “proved”
- 1InspectRead the source, destination schema, permissions, fields, hierarchy, comments, attachments, and links.
- 2ApproveResolve every difference. One receipt binds the exact plan; unresolved decisions cannot start.
- 3Clone safelyRecheck before writes and during the job. Drift or an uncertain outcome stops the work instead of guessing.
- 4VerifyRead targets back from Jira and export the complete source-to-target Evidence Package.
WHY TEAMS USE IT
A clone is not complete just because Jira returned “created.”
Bulk cloning gets risky when fields differ, permissions change, or a response disappears. CloneGuard makes each risk visible and reviewable.
Stop on changed conditions
A changed source, schema, or permission set pauses the job before more writes.
Prove the result
Verified means CloneGuard reread Jira and matched the approved fields and artifacts.
SEE THE CONTRACT
Nothing important hides behind the Start button
01
Review before creation
Work-item types, populated fields, expected differences, and blockers stay visible until the plan is ready.
02
Keep completed work fixed
If the contract drifts, CloneGuard compares the old and new plans. Verified targets remain mapped; only unfinished work needs approval.
03
Export evidence, not a success toast
Every selected source has an explicit result. The browser recomputes the package digest before JSON download or copy.
2,000items per approved contract
0writes to selected sources
15items per execution page
365day operational retention limit
BUILT FOR THE UNCOMFORTABLE QUESTIONS
What happens when something goes wrong?
A write response is uncertain
CloneGuard records intent first and stops rather than risking an automatic duplicate.
A permission disappears
Jira operations run as the initiating user. Current Jira permissions remain the authority.
A result does not match
The target is not called Verified. The mismatch remains visible for repair and read-only re-verification.
CloneGuard runs on Atlassian Forge with no remote backend or external network egress. The Jira app contains no analytics SDK. Analytics on this public website is separate and loads only after consent.
HONEST BOUNDARIES
CloneGuard is for controlled same-site cloning—not migration magic.
- Jira Cloud, within one site
- Does not preserve original authorship or timestamps
- Does not copy worklogs or third-party app data
- Does not bypass Jira permissions
- Does not modify or delete selected source work items
- Does not automatically roll back created targets
QUICK ANSWERS
CloneGuard FAQ
What does CloneGuard do?
It checks and approves a same-site Jira clone, stops when approved conditions change, and verifies the created targets by reading Jira again.
Does it change the original Jira work items?
No. CloneGuard records zero writes to the selected sources.
Can it clone between different Jira sites?
No. The current product supports destinations on the same Jira Cloud site.
What happens when Jira changes during a job?
The job pauses. Completed mappings remain fixed and unfinished items require review of the changed plan.
What is the Evidence Package?
A JSON record of the approval, contract, results, verification outcomes, events, and integrity digest.
AVAILABLE ON ATLASSIAN MARKETPLACE
Make the clone explain itself.
Start with a 30-day evaluation. Every safety and verification control is included.