Linear TEST / TEST2 / ARCHIVE — Audit and Merge/Archive Plan
Date: 2026-03-18
Purpose: Per discovery report Section 6.3 — decide merge/archive for test teams; move client work to the right client team where appropriate.
1. Summary
| Team | Issues | All have project? | Content type |
|---|---|---|---|
| TEST | 43 | Yes | LMNT-style: Wholesale, Ingestion, Data Mart, BI, Contracts, Documentation |
| TEST2 | 42 | Yes | Same as TEST (near-duplicate structure) |
| ARCHIVE | (see below) | — | Archived work |
- Delivery: 0 issues (no unassigned).
- GTM: 6 issues were unassigned → assigned to Outbound SDR/BDR (2026-03-18).
- Sales, Marketing, Operations: No unassigned issues found in sampled list (all had projects or empty team).
2. TEST team
- 43 issues, all with a project. Projects are LMNT-style: Wholesale Data Ingestion, Wholesale Data Mart, Ingestion (Amazon, Shopify, Stord, Ware2Go, etc.), BI Evaluation/Setup/Training, Data Platform Architecture, Metric Dictionary, Snowflake/Polytomic/BI Tool contracts, etc.
- Conclusion: This is a duplicate/copy of LMNT-style work (discovery: “TEST and TEST2 have many projects under Data Service (duplicates of LMNT-style work)”).
- Recommendation:
- Option A — Archive: If no one is actively using TEST for real delivery, archive the TEST team or its projects and leave issues as-is for reference.
- Option B — Move to LMNT: For any issue that represents real LMNT client work (e.g. Wholesale, Ingestion, Reporting), move the issue to the LMNT team and assign to the matching LMNT project (e.g. “LMNT | Ingestion”, “LMNT | Data Modeling”, “LMNT | Reporting and Analytics”). Then archive TEST (or leave TEST for ad-hoc testing only).
- Option C — Keep for testing: Keep TEST as a sandbox; do not move issues to LMNT. Add a team description “Internal test/sandbox — do not use for real client work.”
3. TEST2 team
- 42 issues, all with a project. Structure mirrors TEST: Ingest and Backfill, Wholesale Data Mart, Ecommerce Data Mart, Retail Data Mart, Reporting Platform, Data Infrastructure, Documentation.
- Conclusion: Near-duplicate of TEST; both look like copies of an LMNT-style backlog.
- Recommendation:
- Merge into TEST or archive: Either (a) move all TEST2 issues to TEST (then archive TEST2 team), or (b) archive TEST2 team and its projects without moving issues.
- Then apply the same decision as for TEST (archive vs. move real work to LMNT vs. keep as sandbox).
4. ARCHIVE team
- Used for archived work. No change recommended unless you want to bulk-archive TEST/TEST2 projects into ARCHIVE.
5. Recommended order of operations
- Decide (product/delivery): Is any TEST/TEST2 issue real LMNT (or other client) work that should live on the client team? If yes, list those issues and move them to LMNT (or correct client) and the right project.
- Consolidate test teams: Merge TEST2 → TEST (move issues to TEST, then archive TEST2), or archive both TEST and TEST2.
- Rename or describe: If keeping TEST as sandbox, set team description to e.g. “Internal test/sandbox — not for client delivery.”
- Update discovery report: Mark Section 6.3 as “Audit done; merge/archive per knowledge/sales/linear-test-archive-audit-2026-03-18.md.”
6. References
- Discovery: linear-full-cleanup-discovery-report-2026-03-17.md Section 6.3
- Taxonomy: linear-cleanup-taxonomy.md
- Linear MCP:
list_issues,list_projects,save_issue(move issue to another team requires reassignment to team + project)