Skip to content
Astera Technology

Clone joining tasks without cloning another staff member’s receipts

Copy task definitions while clearing person-bound execution evidence.

Separate definition from execution

Synthetic J10 for S5 is cloned from J8 for S4. Template tasks are desk pack, locker allocation and contact review. J8 has receipts R1/R2/R3 for S4. Local cloning carries task definitions only; J10 gets T10A/B/C with no receipts.

Clone field disposition
FieldCopy?J10 result
Task definitionYesThree tasks
Staff identityNo; use targetS5
Receipt/statusNoAbsent/pending
Download editable CSV ↓

Create person-bound task identities

  1. Read approved task template
  2. Bind J10 tasks to S5
  3. Clear source receipts/statuses
  4. Verify all three pending

A reusable publication reference may be shared, but a staff execution receipt may not.

How many J10 completion receipts may be inherited?

Show the worked answer

Zero. Three definitions are copied; all three target tasks remain pending.

Inspect the clean cloned case

Filled administration checks
CaseAction or resultEvidence boundary
Copy desk-guide publication IDAllowed template referenceDefinition-level shared material
Copy S4 receiptR1RejectActor and case differ
Download editable CSV ↓

Test the clone with a completed source case, not only a blank template, so leaked completion evidence is visible.

Related resources