42 lines
1.2 KiB
Markdown
42 lines
1.2 KiB
Markdown
---
|
|
title: Warning Severity Summary
|
|
category: Warnings
|
|
tags: warnings, severity, continuity
|
|
contextKey: warnings.severitySummary
|
|
micro: See warning counts grouped by seriousness.
|
|
quickTitle: By severity
|
|
quickSummary: By severity helps you decide whether to start with errors, warnings or informational review notes.
|
|
screenshot:
|
|
---
|
|
|
|
# Overview
|
|
|
|
By severity groups warnings by how strongly they need review. Severity is a triage signal, not an automatic judgement.
|
|
|
|
# When Should I Use This?
|
|
|
|
Use it when a project has many warnings and you need to decide where to start.
|
|
|
|
# How To Use It
|
|
|
|
Begin with the most serious items when preparing for revision, but also scan lower-severity notes for useful clues.
|
|
|
|
# Example
|
|
|
|
An error may point to missing required continuity. An informational note may still reveal a useful revision question.
|
|
|
|
# Writer Tip
|
|
|
|
Severity tells you review order, not creative truth.
|
|
|
|
# Common Mistakes
|
|
|
|
- Ignoring lower severity warnings entirely.
|
|
- Treating high severity as always wrong.
|
|
- Reviewing counts without opening the actual warnings.
|
|
|
|
# Related Guides
|
|
|
|
- [Warnings](/Help/Article/warnings.overview)
|
|
- [Story Health](/Help/Article/storyHealth.overview)
|