Skip to main content
Member

Issue statuses

An issue is unresolved, resolved or ignored, and any member of the organization can move it between those statuses. This page explains what each one means, what Collector does in each case and when it tells you.

The three statuses​

StatusWhat it meansAlerts?
unresolved · UnresolvedIt's happening and nobody closed it. Every new issue starts here.Yes, when it appears.
resolved · ResolvedSomeone fixed it.Yes, if it happens again.
ignored · IgnoredKnown, and it doesn't matter: noise from an old browser, an expected error.No. Its events keep counting, but it sends no email and doesn't change status.

Changing the status​

On the issue's page:

  • Resolve marks it resolved.
  • Ignore marks it ignored.
  • Reopen takes it back to Unresolved, from either of the other two.

The change is immediate for everyone: the list and the page of whoever has them open update by themselves.

When a resolved issue comes back​

If an event arrives for a resolved issue, Collector reopens it: it goes back to Unresolved, the list marks it REGRESSED and the page shows when it came back and in which release. It's the sign that the fix wasn't enough, or that something undid it.

An ignored issue doesn't come back: it stays ignored even as events arrive.

The emails​

Collector sends an email at two moments:

  • when a new issue appears, with its title as the subject;
  • when a resolved issue comes back, with the subject Regressed: ….

Every member of the organization gets it, each in their own language, except whoever muted the project. A burst of events on the same issue is one email, not a thousand.

Assigning someone​

Assignee says whose an issue is on the team. Pick any member of the organization, or Unassigned. Assigning doesn't change the status or send emails: it's so the team knows who's looking at it.

The record​

Every status change, every assignment and every issue that comes back goes into the audit log, with who did it and when.

Issues that merge​

When you upload a release's source maps after its errors arrived, Collector regroups those events by your original code. Sometimes that merges two issues that were the same. Links to the issue that went away, including those in emails already sent, lead to the one that stayed.

From the terminal​

collector issues resolve 2C7ZffP787kc 3D8AggQ898ld # several at once
collector issues ignore 2C7ZffP787kc
collector issues reopen 2C7ZffP787kc
collector issues assign 2C7ZffP787kc ana@company.com # or me, or none