Use cases
Review recorded activity around your launch.
Compare issue updates, pull requests, and support tickets from the launch period.
Connected activity
4 events from 4 sourcesGitHub · Linear · Zendesk · Stripe
- GitHubRelease pull request mergedMerged
Event from this source
- LinearRelease issue closedCompleted
Event from this source
- ZendeskLaunch ticket updatedUpdated
Event from this source
- StripePayment receivedRecorded
Event from this source
Connected sources
5 sources connectedThe situation
A release recap can require searching engineering and support tools separately.
Compare issue updates, pull requests, and support tickets from the launch period.
The workflow
Try it before your next update
- 01
Configure the sources you want to follow. Free includes two integrations.
- 02
Look through activity from the launch period. Inspect relevant events, then follow a source link when you need more detail.
- 03
Inspect recorded work around the release.
What you see
Examples of recorded activity
Available events depend on your source configuration.
- 10m agoGitHub
Release pull request merged
- 2h agoLinear
Release issue closed
- 4h agoZendesk
Launch ticket updated
- YesterdayStripe
Payment received
- 2d agoGranola
Launch meeting note available
The outcome
Inspect recorded work around the release.
Check support updates from the same period.
Keep findings separate from assumptions about what caused them.
Questions
Before you get started
Does a merged pull request mean the change is live?
No. Check your release or deployment system to confirm what reached production. The feed shows the source events it has collected.
Which plan do I need?
Start with two built-in sources and seven days of searchable history on Free. Starter includes five sources and 60 days; Pro includes eight sources, 365 days, and custom integrations.
Get started