At a glance
Every problem opens with a plain-language title and description that Interfere writes for you, so you know what you’re looking at before reading a single stack trace. Alongside it you’ll find:- The evidence behind it. Every piece of evidence that rolled up into this problem, linked so you can drill into specific occurrences.
- Who it affected. How many users hit it and how often, and the users themselves, so you can gauge impact instead of guessing.
The timeline
The timeline is the heart of the problem view: one chronological thread of the investigation and the work around it.- It updates itself. Interfere advances the status as it investigates and only pulls you in when it needs a human decision, like confirming a likely regression. You’re not babysitting a queue.
- Root cause, code, and facts. The timeline lays out what Interfere found: the likely cause, the relevant code, and the facts behind it, so the reasoning is in front of you rather than hidden.
- Linked pull requests. Pull requests that relate to the problem appear on the timeline, so a fix in flight sits next to the problem it addresses.
- Relevant sessions. Jump straight to the session replays where the problem actually appeared, so you spend your time on where it shows up in a real user’s flow.
- Filtering. Filter the timeline down to the part you care about when there’s a lot going on.
Collaborate
A problem is rarely one person’s job, so the timeline is where your team works it together.- Assign it. Hand a problem to the right teammate.
- Discuss inline. Comment and mention people on the timeline to pull in whoever’s needed, from the engineer who owns the code to a designer or PM.
- Get notified. Interfere notifies the right people when a problem needs them. Choose where those notifications go in Alerts.
- Carry it into Slack. Mentions and assignments reach you as Slack messages, and you can keep the conversation there. See Slack or open the Slack integration.