Skip to main content
In client email you said “bug.” In Jira they said “defect.” In SimpleUAT the UI is Findings (route /defects). It’s the same object: something wrong, with proof.

Log it two ways

  • Fail a step during a run: the UI can prompt you to file an issue.
  • Log a finding standalone: allowed. Use it for exploratory, or for issues that aren’t tied to a scripted step.

Fields you’ll actually use

  • Severity: trivial | minor | major | critical | blocker
  • Status: open | in_review | resolved | closed | wont_fix | retest
  • Priority: low | medium | high | urgent
  • Comments, evidence, Jira Links
Jira: generate/attach links from issue keys. This does not sync with Jira. No API two-way. GitHub Issues can create issues from defects if connected. Jira vs GitHub.

Evidence

PNG, JPEG, GIF, WebP, PDF, WebM, MP4, 25MB. On runs, steps, and findings. Evidence. Write findings like you would a good ticket: what you did, what you expected, what happened, where (environment URL), who you were (persona). The delivery snapshot will carry this; you won’t rewrite it in Word unless you want to.

Failed vs finding

A fail is a result. A finding is the issue record.

Retest path

Your retest status and the client’s request.