User guide

Signals QA Bam Instructions

Capture useful evidence, prepare a clear Bam, and move it into team triage.
Back to dashboard

The working loop

From unexpected behavior to an actionable report

A strong Bam shows what happened, preserves the technical context, and reaches only the team that should act on it.

Signals Capture v1.0.15
Record Tab
Record Screen
Record audio (microphone and source)
Take screenshot
Go to Bam
  1. 1CaptureRecord the shortest reliable reproduction.
  2. 2ReviewTrim and annotate the evidence.
  3. 3DescribeReplace placeholders with useful context.
  4. 4RouteSelect teams, tags, and badges.
  5. 5ShareMake the Bam visible to those teams.
  6. 6ResolveCollaborate, create Jira work, and close.
01

Access and roles

Your role determines whether you review existing Bams or create and triage new ones.

Viewer

Reviews shared Bams and any private Bam owned by one of their teams, and can participate in comments.

Creator

Captures issues, edits Bam metadata, shares with teams, and creates Jira tickets.

Power user

Has creator capabilities and broader Bam visibility for cross-team support and triage.

Getting accessUse Request Access on the dashboard with your Revvity email, requested role, and team. Your account email contains the API key used to sign in and configure capture.
AdminsAdmins additionally manage users, teams, and badges from the Admin page, and can open a full Audit Trail (in a separate tab) of every Bam change and admin action. API key show/rotate actions are never recorded there.
02

Capture the problem

Begin close to the failure and stop as soon as the useful evidence is complete.

Choose a capture mode

  • Record Tab for activity inside the current browser tab.
  • Record Screen when the workflow crosses windows or applications.
  • Take screenshot for a stable visual defect; select only the relevant area.
  • Enable Record audio only when narration adds information the screen cannot show.

Capture well

  • Start from a known state and reproduce one problem per Bam.
  • Pause briefly before and after the failure so reviewers can orient themselves.
  • Avoid exposing unrelated customer data, credentials, or private conversations.
  • Use the recording pill to pause or stop without reopening the extension.
03

Review before upload

The review window is the last chance to make the evidence concise and obvious.

1

Play the capture. Confirm that the failure and the steps leading to it are visible.

2

Trim dead time. Set start and end points around the useful sequence.

3

Annotate key frames. Use pen, text, rectangle, or circle to direct attention.

4

Upload or cancel. Upload creates the evidence; Cancel removes the unfinished Bam.

Keep the review window open while upload and processing complete. It closes automatically after success.

04

Prepare the Bam

Metadata autosaves. Watch for the Saved status before navigating away.

Summary

Name the failed workflow and observable result. Replace the generated placeholder.

Description

State the setup, expected result, actual result, and a short reproduction recipe.

Tags

Use reusable global labels for product areas or issue categories.

Badges

Add team-scoped work area or context labels. Badges help filtering but do not grant access.

Resolution

Keep active work Open; mark it Closed after verification or a decision not to proceed.

Credentials

Provide the tenant user and password needed to reproduce, or explicitly select the waiver.

AI suggestionSuggest summary & description uses only recorded interaction details after redaction. Review and correct every suggestion before sharing.
05

Route and share safely

New Bams are private. Sharing is an intentional handoff to selected teams.

Private

Visible to the creator and any user on one of the Bam's assigned teams. Power users and admins retain oversight visibility.

Shared

Visible to every signed-in user, regardless of team. Badges never broaden visibility.

Before selecting Shared

  • Select at least one team that owns or needs the report.
  • Enter Tenant User and Password, or select User and Password not required.
  • Confirm the summary and description are ready for readers outside the capture context.
  • After sharing, use Copy link to send a direct URL. Recipients still need permitted access.
06

Investigate the evidence

Use each detail tab to answer a different question about the failure.

Info

Media, metadata, teams, badges, credentials, HAR download, and Jira actions.

Console

Warnings and errors emitted during the captured workflow.

Network

Requests, status codes, timing, headers, and available request or response payloads.

User Actions

Clicks, input changes, form submissions, navigation, and selected keys in sequence.

App Data

Captured browser state and performance timing available at stop.

Recorded URLs are reduced to unique origins. Sensitive credential fields and captured payloads are redacted where supported.

07

Collaborate and resolve

Keep decisions and follow-up close to the evidence.

  • Add comments for findings, questions, and verification results.
  • Mention a teammate with their full email address to notify them and add them as a watcher.
  • Use Copy for Jira when another workflow needs a formatted diagnostic summary.
  • Close the Bam when the fix is verified or triage is complete; Re-open it if the issue returns.
08

Create Jira work

Create a ticket only after the Bam is readable and reproducible.

Required preparation

  • Replace the placeholder summary.
  • Supply credentials or select the waiver.
  • Select project, Fix Version, Reported in Build, Defect Type, Priority, and Deployment Target.

What is transferred

  • Bam details and a link back to the source report.
  • Recording, HAR, and annotation images when available.
  • Tags and selected team badge names as sanitized Jira labels.
After creationThe Jira key appears in Info. Use Update from Jira to bring the Jira description back into the Bam.
09

Find the right Bam

Combine filters to reduce the list without closing the currently open detail.

MinePrivateSharedOpenClosedHas JiraTeamBadgeTag
  • Search matches the Bam ID, summary, description, tags, capture data, creator, teams, and other Info fields.
  • Team, badge, tag, privacy, resolution, Mine, Jira, and search filters work together.
  • Selecting multiple teams narrows the list to Bams assigned to every selected team; badge and tag filters still match any of their selected values.
  • Use Clear filters to reset the complete filter state.
  • Use Full list for scanning many Bams; hide the list when focused investigation needs more space.
10

Ready-to-share checklist

A one-minute quality check prevents most triage back-and-forth.

  • ✓The capture shows one clear problem and no unnecessary sensitive data.
  • ✓The summary names the workflow and failure.
  • ✓The description states expected versus actual behavior and reproduction steps.
  • ✓The correct owning or collaborating teams are selected.
  • ✓Credentials are supplied, or the waiver is intentionally checked.
  • ✓Tags and badges are useful for future searching and reporting.
  • ✓The Bam is Shared only when it is ready for its selected teams.