SEVERITY
Severity 4 (Trivial)
Cosmetic issues, typos, or internal-only problems. Zero user impact.
SEV4
Cosmetic issues, typos, or internal-only problems. Zero user impact.
## "Polish and Nits" **SEV4 (Severity 4)** is for cosmetic issues, documentation typos, or internal tool glitches that don't stop work. ### Examples * A typo in the FAQ. * A button is 2 pixels off-center. * A deprecated warning in the consolelogs. ### Response Fix it if you are already in the file. Otherwise, backlog it.
ExThe Typo
"The about page said "We are the bestt"."
Impact
Embarrassment.
Resolution
Fixed in 2 minutes.
Why SEV4 Matters
Lowest priority. Fix when time permits.
Good tasks for onboarding new engineers.
Common Pitfalls
Bikeshedding
Spending 3 hours debating a SEV4 color shade.
Ignoring Them Forever
SEV4s piling up creates "Broken Window Syndrome". Dedicate a "Polish Week" to clear them.
How to Use SEV4
👋
Onboarding: Great first task for new hires.
✨
Polish: Fixing these shows you care about quality.
Related Terms
Frequently Asked Questions
Why track this?
To quantify "polish" work and prioritize quality weeks.
Do SEV4s need a postmortem?
Never. Fix the typo, close the ticket, and move on.