Skip to content

Bug Report Template

⚠️ Please fill out all sections. Incomplete reports may significantly delay investigation. Alternatively, you can submit a bug report through TestFlight or the Play store if more convenient.

1. Clear & Concise Title

A short description that summarizes the issue.

Example: Wallet app hangs on mdoc presentation during data transfer

2. Environment Details (Required)

Provide exact and complete environment information.

  • Application version
  • OS (including version)
  • Browser (including version)
  • Device (if mobile)

3. Preconditions

List anything that must already be true before starting reproduction.

4. Detailed Steps to Reproduce (Critical Section)

Assume our Developer Team knows nothing about your context. Be precise. Avoid vague phrases without specifying exactly how to reproduce the behaviour.

Required qualities:

  • Deterministic
  • Numbered steps
  • Includes exact inputs
  • Includes button names clicked
  • Includes timing details (if relevant)
  • Includes screenshots or logs if helpful

Format:

  1. Start from ..
  2. Navigate to: ..
  3. Click "Start": ..
  4. Enter the following values:
    • Field A: value123
    • Field B: 0
  5. Click "Submit

Expected outcome at this step (if applicable): ...

Actual outcome observed: ...

5. Actual Behaviour

Describe exactly what happens.

Include: - Error messages (copy-paste, do not paraphrase) - Stack traces - HTTP status codes - Console logs - Screenshots (if UI issue) - Logs with timestamps - Frequency (Always / Intermittent / 1 out of 5 times)

Example:

POST /api/validation → 500 Internal Server Error
TypeError: Cannot read property 'id' of undefined

6. Expected Behaviour

Describe what should have happened instead.

Be specific:

  • Should validation block submission?
  • Should UI display an error?
  • Should API return 400 instead of 500?
  • Should value be persisted?

7. Impact Assessment

  • Severity: (Critical / High / Medium / Low)
  • Business impact:
  • Is there a workaround?

8. Regression?

  • Did this work before? (Yes / No / Unknown)
  • If yes, last known working version:
  • Related PR / ticket (if known):

9. Additional Context

Attach any relevant:

  • Screenshots
  • Logs
  • Related tickets
  • Hypotheses (optional, clearly marked as speculation)

10. Submit your report

You can submit your report posting your filled in template in the #bug-reports channel in mattermost. Thank you for taking the time to submit a thorough report. High-quality reports significantly reduce time-to-fix and prevent wasted engineering effort.