Skip to main content
Use custom fields when your team triages findings by criteria Mo does not report on its own, so each bug arrives already labeled.

Add a field

  1. Go to Settings > Mo > Custom fields.
  2. Click Add field and fill in:
    • Name: the key the value is stored under, such as Severity.
    • Description: how Mo should fill out the field.
    • Field type: the kind of value Mo returns.
  3. For Select and Multiselect, add options. Give each option a name and a description of when Mo should choose it.

Write descriptions that steer Mo

Mo has no other context for a field, so the field and option descriptions are the prompt. Say what the value means, what to base it on, and how to decide between close cases:
Concrete criteria give more consistent values than labels alone. Mo picks only from the options you define, so cover every case you expect.

Where values appear

  • Bugs get values only once Mo reproduces them.
  • Values show on bug details in the session, and in the customFields object of the exported session report.
Start a new session after you change fields. A session that is already running can keep using the fields it started with.

Limits

  • 50 fields for bug reproductions.
  • 100 options per Select or Multiselect field.
  • 100 characters per field or option name, 2,000 per description.
  • About 32 KB in total, counting field and option names, descriptions, and types. Over that, saving fails even if each field is within its own limits; shorten names or descriptions, or remove fields or options.