Logging Results

Logging a result is the core action of an exploration — write what you found, mark it with a status, and add it to the timeline. Each result entry is a self-contained observation: notes describing the finding, a status indicating the outcome, and optional evidence like inline images and linked issues. Every entry is timestamped, attributed to the tester, and preserved permanently.

Think of it as filing a field report

Each result entry is a field report from the field. Describe your observations (notes), classify the finding (status), attach photographic evidence (inline images), and reference any tickets filed (linked issues). Each report is stamped with your name and the time — and joins a permanent record that the whole team can review.

Step by step

1. Open an exploration from the EXPLORATIONS tab.
2. Scroll to the Session Log card on the detail page.
3. Write your observations in the rich-text editor. Use formatting — headings, lists, code blocks — for clarity.
4. Select a Result Type from the dropdown — for example, Passed, Failed, or Blocked.
5. Click Add.
6. The entry appears immediately in the results timeline below the session log.

The notes editor

The rich-text editor supports: bold, italic, underline, strikethrough, headings, bullet and numbered lists, code blocks, blockquotes, links, and inline images. Use these tools to write clear, structured observations.

The editor is disabled when the exploration is closed — no new results can be logged on a closed exploration.

Choosing a result status

The Result Type dropdown shows all statuses that are scoped for explorations. The “Untested” status is excluded since every logged result represents an active observation.

Statuses are configurable. Status names, icons, and colours are managed in Statuses. Which statuses appear in the dropdown is controlled by scope availability — see Scope Availability.

Uploading images

1. Drag an image file into the editor area, or paste from your clipboard.
2. The image uploads in the background and a preview appears inline in the editor.
3. Click Add to permanently attach the image to the result entry.

Save before navigating away. Images uploaded during a draft are stored temporarily. If you navigate away from the page without clicking Add, draft uploads may be discarded.

Linking external issues

After a result is logged, you can link external issues (from Jira, GitHub, Azure DevOps, or other configured sources) to individual result entries. Linked issues appear on the result card with a count badge and are also aggregated in the sidebar Issues card.

Linking issues requires the Manage external references permission. For full details on configuring issue sources and relation types, see External References.

Filtering results

Use the filter dropdown at the top of the results section to show all result types or only results with a specific status. This is useful for reviewing only failures, isolating blocked items, or focusing on a particular category of finding.

Result history

Every result entry is preserved permanently in reverse-chronological order. Results are never overwritten or deleted — each entry is a standalone record. This provides a complete audit trail of what was discovered, when, by whom, and what status was assigned.

Exploration results vs test run results