Skip to content

Draft improvements from assistant conversations: first seen vs last seen #8

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mintlify wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Draft improvements from assistant conversations: first seen vs last seen #8

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3404d93
docs: explain first seen and last seen on the problem view
mintlify[bot] Jul 6, 2026
a2dc9c5
docs: tighten first seen and last seen wording
mintlify[bot] Jul 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions product/problems.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,7 @@

- **The evidence behind it.** Every [piece of evidence](/concepts#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](https://interfere.com/~/*/users) themselves, so you can gauge impact instead of guessing.
- **First seen and last seen.** *First seen* is when Interfere recorded the earliest piece of evidence for this problem. It tells you whether the problem just appeared or has been running for a while. *Last seen* is the most recent occurrence, so you can tell whether it's still happening or has gone quiet. Together they bound the window the problem has been active. When a resolved problem returns as a [regression](/concepts#regression), *last seen* advances to the new occurrence and *first seen* stays put.

## The timeline

Expand All @@ -33,7 +34,7 @@
- **Assign it.** Hand the problem to the right teammate. Press <kbd>a</kbd> to open the assignee picker.
- **Set priority.** Mark it high, medium, or low so the team knows what to pick up first. Press <kbd>p</kbd> to set it.
- **Edit the title or description.** Interfere writes both for you. Tighten either one if you want it to read a certain way for your team.
- **Discuss inline.** Comment on the timeline and @mention people to pull in whoever's needed, from the engineer who owns the code to a designer or PM.

Check warning on line 37 in product/problems.mdx

View check run for this annotation

Mintlify / Mintlify Validation (interfere) - vale-spellcheck

product/problems.mdx#L37 

Did you really mean 'whoever's'?
- **Subscribe.** Follow a problem to get its updates, or unsubscribe to step back. Press <kbd>s</kbd> to toggle it.
- **Dismiss it.** When a problem isn't worth acting on, dismiss it to clear it from your active list. Interfere keeps the record in case it returns.
- **Archive it.** Remove a problem you don't want to see at all.
Expand Down