Back to Blog

A bug report template copied from the run

The issue markdown Monito copies: title, steps, expected, actual, environment, and a link to the run. You paste it into the tracker.

bug-reportevidence

Monito does not create the ticket. On a bug in the run report, Copy as issue puts markdown on the clipboard. The CLI prints the same body:

monito run view <id> --issue-markdown

With --json the shape is { "runId", "issues": [{ "bugReportId", "markdown" }] }. If the run failed or errored, the process exits 1. If there are no bug reports, the message is "No bug reports for this run."

The fields

The markdown is built from the bug and the run, in this order:

  1. A title (#). If the bug has no title, the heading is "Untitled bug".
  2. Description, only when the bug has one.
  3. Steps to reproduce.
  4. Expected behavior.
  5. Actual behavior.
  6. Environment: the environment name, and a link labeled "Tested URL".
  7. Evidence: a "View run report" link. A public report may also include a link to the first public screenshot. A private report does not add a screenshot URL.

Empty text becomes "Not provided." URLs in the body are stripped of userinfo, query, and fragment. A value that looks like a masked credential is replaced with "credential omitted." That is the sanitizer in formatIssueMarkdown. Do not expect a raw cookie or a query string to survive the copy.

What you still write

The copy is the evidence from Monito's run, not from a customer session. You choose the tracker, you paste, and you set priority. Jira, Linear, and GitHub Issues all accept markdown. None of them is connected.

A check that could not verify the scenario is an Error, not a bug report you should file as an app bug. Read the cause first. What cannot verify means.

Sign up and run the scenario. The report is where Copy as issue lives.