Linear — data prerequisites for honest views and filters
Purpose: Label- and initiative-based saved views only work when underlying data matches policy. Run these before treating dashboard or filter counts as governance truth.
Audience: Head of Delivery, Platform ops, or whoever owns workspace hygiene.
When to run
- After a large taxonomy or team reorg
- Before quarterly portfolio reviews that use service line or offering filters
- When CSOs or SLs report “the view is wrong” (orphan issues, missing initiatives)
Skills and playbooks (read-only or apply)
| Need | Skill / doc |
|---|---|
| Issues missing team + project + initiative linkage | .cursor/skills/linear-structure-hygiene/SKILL.md (full mode: I1+I2+I3) |
| Issues missing project only (assign to correct project; optional duplicates) | Same skill — Appendix A (I1-only); alias .cursor/skills/linear-tickets-to-projects/SKILL.md |
| Engineering issues missing service / subservice labels | .cursor/skills/linear-service-label-audit/SKILL.md (audit); .cursor/skills/linear-service-label-apply/SKILL.md (apply after human-approved mapping) |
| Taxonomy reference | linear-cleanup-taxonomy.md |
Related
- linear-day-1-guide.md — full onboarding; labels vs Operating roster for SL views
- linear-custom-views-audit.md — list and maintain custom views