Skip to main content
Every bug in a Mo report starts untriaged. Your decision is recorded on the bug, with who made it and when, so the next reader sees it.

​
The decisions

Reset clears a decision and returns the bug to untriaged.

​
Works as intended

Mo reports an intended behavior again on the next run unless the run knows about it, so a works-as-intended decision records the reason:
1

Explain why the behavior is expected

Type the reason, for example “The confirmation modal is intentional. It prevents accidental deletes.”
2

Review the suggested entry

Mo drafts a knowledge base entry from your reason and the bug, or matches an entry that already covers it.
3

Accept or reject it

Accept and the entry is saved and linked to the bug. Reject it, or choose Skip knowledge, and the bug is still marked as intended with no entry written.
Momentic retrieves the relevant knowledge entries on every AI-assisted step, so a later Mo session reads the entry while it explores that flow and does not report the behavior again. Your Momentic tests use the same entries. The linked entry stays visible on the bug. If you change the decision later, Mo asks whether to unlink the entry as well.

​
What to do with an accepted bug

Fix it, then keep the flow covered by writing the case as a Momentic test.