Bugs
A bug outlives the hunt that found it. The Bugs screen is every bug from every bug hunt in the organization, in one list — the view a single hunt screen cannot give you.
Statuses
| Status | Meaning |
|---|---|
| Open | Filed, nobody has picked it up |
| In progress | Somebody is on it |
| Done | Fixed, or otherwise settled |
| Won't fix | A decision was made to live with it — requires a reason |
The list opens on Open and In progress, because a list that opens with every bug ever filed is a list nobody reads. The settled ones are one click away, and the counts in the filter labels are computed over every status, so the tabs can tell you how many are Done while showing you what is not.
:::info "Open" means two statuses, everywhere
Open and In progress both count as open — in this list, in a test case's
known issues, and in requirement coverage. A bug somebody picked up must not
stop counting against the requirement it threatens.
:::
:::caution Session bugs are a separate list with different words
Bugs logged in an exploratory session use Open, Resolved,
Closed and live on the session. They were not part of the move to the
four-word list and do not appear here.
:::
Severity
Low · Medium · High · Critical. Severity is what the bug does, not how
soon somebody will do something about it — that is what status is for.
Filtering
The standard toolbar applies: search, plus filters for status, severity, reporter, hunt and tag. Selections go into the URL, so a filtered list is a link you can paste into a chat.
The status filter uses a fixed set, so unticking everything shows nothing rather than silently reverting to the default. Filters that grow from your data — reporters, tags — treat "nothing ticked" as "everything".
Won't fix, and the reason
The reason is enforced on every path that can set the status: creating the bug,
editing it, and the dedicated status control. It is cleared when a bug moves
back out of Won't fix, so a stale justification never reads as though the
decision still stood.
Where else bugs show up
- On the bug hunt that found them
- On the test case, under known issues, while still open
- Against a requirement, holding its coverage down while any linked case has an open bug
- In a Jira issue's remote links, if the integration is connected