← Back to parent Epic
MAZENG-FT-37 · Create a project from a selected template
Why it matters
A user needs to start a new editable project from a proven template instead of rebuilding the design.
Expected outcome
An independent project copy provides a fast starting point without coupling later edits to the template.
In scope
- Collect the new project name and description.
- Atomically clone the template resource and canvas data into an independent project.
- Assign the requesting user as owner and increment usage only after success.
- Delivery status
IN_BACKLOG- Owner
- RootAtSkic
- Solution approval
- PENDING
Acceptance
Acceptance outcomes
- 01
The user selects a template and supplies a new project name and description.
- 02
The new project receives an independent copy of resource and canvas data.
- 03
The requesting user becomes the project owner.
- 04
Template usage is incremented only after successful project creation.
- 05
The user is taken directly to the created project.
Dependencies and risks
Dependencies
None recorded.
Risks
- Cloning requires a transaction so partial project, resource, or member records are not retained.
- Legacy creation uses multiple independent writes and a raw usage update.
- Source-control metadata and broader collaborators are not copied by legacy behavior.
Authoritative Architecture tasks
No authoritative Architecture tasks are linked.