Ticket screenshot chains: one tall PNG tells the story—redact logins, tokens, and internal URLs first
`screenshot-sequence-merge` chains multi-window repros for engineering. Risks are URL queries, cookie banners, test-account email leakage, and mixed macOS/Windows density. Legal may require keeping timestamps—or forbidding them—know the policy before cropping. Prefer one scroll capture when it stays under size limits; if you segment, label “2/4” continuity.
`screenshot-sequence-merge`: redact, sort, merge, then describe environment and branch in the ticket body
- Per frame scrub address bars, cookie banners, avatars, and debug HUDs; reproduce on sanitized accounts. Keep status bars when policy demands provable time; mask device identifiers when forbidden.
- Normalize logical width, merge vertically, and insert slim color bars labeled “Step 3→4”; annotate platform at segment starts when OS chrome differs. Use crisp key frames instead of motion-blurred stills.
- Upload PNG to the ticket plus an MD5 or immutable object link; for incidents maintain lawyer-visible vs public redaction tiers.
Screenshot chain FAQ: session leakage, status bars, mixed DPR, scroll vs segments
URL is redacted yet security still sees session exposure—where else?
Check WebSocket panes, local storage modals, clipboard toasts, and DevTools network columns—rectangle redaction plus captions beats masking only the omnibox.
Legal wants timestamps but marketing wants them cropped—who wins?
Follow data classification: external marketing may crop; fraud or billing evidence may require timestamps cross-referenced to server logs. Get it in writing.
Mix of 125% and 100% browser zoom in one chain looks like two products—fix?
Re-capture on one zoom level when possible; if not, banner each segment (“125% Windows / 100% macOS”) and avoid side-by-side comparisons that imply parity.
Android vs iOS shots in one review feel unprofessional—unify or stay authentic?
External comms often need a shared frame template; internal bugs should stay faithful with explicit platform tags. Brand the outer border, not the pixels.
Scrolling capture vs four manual segments—when to choose which?
Prefer one scroll capture when size stays reasonable and lazy-load gaps are absent; otherwise segment with 20px overlap to prove continuity.