Internal Tools, Access & Reporting Bugs

This page covers the tools and processes you will use as an internal team member for testing the platform, reporting bugs, and staying up to date on what has shipped.

Communication

Microsoft Teams channel: The primary async channel for the internal team. Use it for questions, quick updates, and flagging issues that do not yet need a formal bug card.

Bug reporting workflow

When you encounter a bug during testing, use this three-tool workflow:

1. Burning Bugs: capture the video

Before anything else, record a short screen-capture video of the bug in action. Burning Bugs is the tool used for this. Video evidence is more useful than a text description alone because developers can see exactly what UI state preceded the failure.

2. Microsoft Planner: create a bug card

Once you have your video, log the bug in Microsoft Planner. A bug card should include:

A clear title describing the failure
The steps to reproduce it
The video (or a link to it)
The severity (cosmetic vs blocking vs data-loss risk)

Access to Planner will be granted by the team lead. New team members should expect to spend their first week or two testing and filling Planner cards before being given direct access to Sprint.

3. Sprint: for critical bugs

Sprint is the issue tracker where critical bugs get formally raised for engineering. For most early testers, a senior team member will triage Planner cards and escalate the critical ones to Sprint. Direct Sprint access is granted once you are comfortable with the process and your bug quality is consistent.

Platform documentation

resource.consumr.ai: The external-facing resource site where release notes are published. Check here to understand what features have shipped, what has changed, and what the self-serve documentation says. It is the authoritative source for current feature state.

Research support contact

For questions about specific research types, survey design, or how to interpret results, there is an internal research support contact. The email address heard in the training session was partially garbled; see Open Questions for the status on confirming the exact address.

What counts as a bug worth reporting

Report anything that:

Prevents a user from completing a standard flow (blocking)
Produces unexpected output silently (data risk)
Displays broken UI that a user would flag as “the tool doesn’t work”

Cosmetic issues (like the orange-text-on-orange-background reported in the March 2026 sessions) are also worth logging. Clients notice. See Roadmap & Known Issues for a summary of known issues at time of recording.