Skip to main content
Every finding starts in Needs review. Change it from the finding’s status menu or with qa bugs.
Triage menu open on a cart-total finding, alongside expected and actual behavior

Choose a triage decision from the finding's status menu

Mark fixed records who marked the bug fixed and when; it doesn’t verify the fix. A retest that reproduces the bug sets it to Open. A blocked or incomplete retest leaves the status unchanged. Static flags use a screenshot recheck and keep their status.

File the bug

Open Create issue on the finding and choose Create Linear issue, Create Jira issue, or Create GitHub issue. Edit the prefilled title and description; the finding keeps the link. Jira needs the Atlassian connection in Settings > Integrations, and GitHub needs the Momentic GitHub App with Issues: write. See Linear and Jira. To file elsewhere, export the report and paste each bug’s issue draft, or let your coding agent file it with its tracker tools. See export the report. Status changes in Mo don’t update the linked issue.

From the CLI

Pass the bug id or its exact name. Output is JSON with lifecycleStatus (NEEDS_REVIEW, OPEN, FIXED, DISMISSED, or null for unknown future states) and dismissalReason. CLI decisions don’t create tracker issues or knowledge entries. The legacy qa bugs set-status still works.

Retest

Choose Retest on the finding, with optional Instructions such as the account or URL. Mo gets the bug’s expected behavior, actual behavior, and steps as a message in the original session.

Review findings across sessions

Findings in the Mo sidebar lists every session’s bugs, newest first, for the last 30 days by default. Filter by date, Triage outcome, and platform, or search by bug name, summary, or session title. Open a finding to triage it without opening the session. Filters live in the URL. Analytics > Mo shows reported bugs, flags, acceptance rate, review backlog, and outcomes. The Reported bugs and Confirmed bugs card descriptions link to the matching findings.

Works as intended

Dismiss as Works as intended in the app and type the reason. Mo drafts a knowledge base entry you can edit. If an entry already covers it, the dialog says Already covered by Mo’s knowledge. Accept the entry and later sessions can retrieve it as guidance when it’s relevant. Mark without knowledge dismisses without an entry. Scope the entry to the environments and flows where the behavior is intended. Moving a finding off Works as intended unlinks its knowledge entry but doesn’t delete it. Moving a finding back to Needs review clears its fixed state.

Pull request runs

On a GitHub-triggered session, Allow for this PR keeps an Open bug from blocking that PR’s run. A new PR run needs its own allowance. Triage changes refresh the PR comment and check. To keep a fixed bug covered, turn it into a regression test.