Clone RFI Template - Per-Category Checklist Status
Cloning an RFI template now stamps a category-specific default status on each new checklist item so the checklist reflects the RFI request
Overview
Before Release 3.9, cloning an RFI template onto a project left every new checklist item with status TBA, regardless of the RFI's intent. Gio's feedback from Trello HAPKMldV:
When a checklist is cloned or generated from a template, the checklist status should also be updated accordingly not just the RFI. For example, the checklist items are linked to RFI items, if those items are being requested via the RFI, the corresponding checklist responses should be updated to "No" rather than remaining as "TBA."
Release 3.9 applies a category-specific default status on clone so the checklist accurately reflects what each RFI is asking for.
Category Mapping
| Checklist category | Status on clone |
|---|---|
| Admin | No |
| Part 5 | Non-Compliant |
| SLHC | Non-Compliant |
| Everything else (NCC, Planning, Plan of Subdivision, etc.) | TBA (unchanged default) |
Behaviour Rules
New checklist items
When the clone creates a new ProjectChecklistItem, it uses the resolver to pick the default status from the above table. The item lands pre-stamped so the admin doesn't have to open it up and set "No" / "Non-Compliant" manually.
Existing checklist items already on the project
When the clone hits an item that already exists on the target project:
- If current status tag is
tba(unset / default): flip to the new category default. Treats TBA as "unassigned" and fills it in. - If current status is anything else (Yes / Non-Compliant / Compliant / etc.): leave alone. User-set statuses are preserved so the clone can't clobber manual input.
RFI items
Cloned RFIs continue to land with status Pending, matching the existing spec. That behaviour is unchanged.
Implementation
In the Clone RFI Template handler:
- A
$resolveChecklistStatusclosure centralises the category-to-status mapping. Future category additions plug in here. - Applied on both the new-item creation path and the existing-TBA refresh path.
- The closure returns the
ProjectChecklistItemStatusentity matching the tag (no,non-compliant, ortba), pre-loaded from the repository.
Preprod Verification
Tested on preprod against project 5887 (Royston Homes, AHB Group ISD Checklist Part 5 template) on 22 April 2026:
- Before deploy: post-clone, all 25 template-linked checklist items stayed on TBA across Admin (16), Part 5 (8), and NCC (1).
- After deploy: post-clone, 16 Admin items flipped to
No, 8 Part 5 items flipped toNon-Compliant, 1 NCC item remainedTBA. Non-template checklist items untouched. RFI items all landed asPendingas expected.
Before/after screenshots on the Trello card.