Skip to main content

← Back to parent Epic

MAZENG-FT-13 · Clone an existing project

Feature intent

A user needs to reuse an established project instead of rebuilding similar work.

Why it matters

A user needs to reuse an established project instead of rebuilding similar work.

Expected outcome

Shortens setup for variants, experiments, and repeatable designs.

In scope

  • Clone an accessible active project under a new name and description.
  • Carry forward the source project's resource or canvas state and tags.
  • Create the clone as a distinct project linked to its source.
Delivery status
IN_BACKLOG
Owner
RootAtSkic (product lead)
Parent Epic
MAZENG-EP-3
Solution approval
PENDING

Acceptance

Acceptance outcomes

  1. 01

    A successful clone creates one distinct project linked to the selected source.

  2. 02

    Copied resource or canvas content and tags are available when the clone opens.

  3. 03

    Changes to the clone do not alter the source project.

  4. 04

    A failed clone leaves no partial project.

Dependencies and risks

Dependencies

None recorded.

Risks

  • Legacy cloning copies every member and role, crossing into MAZENG-EP-4 and potentially exposing the clone unnecessarily.
  • Whether a clone starts private, copies selected collaborators, or copies all collaborators requires an explicit product decision before approval.

Authoritative Architecture tasks

No authoritative Architecture tasks are linked.

Original source