Skip to content

Triage

This page is for the maintainer. On every ticket, under the title block, the maintainer sees the Triage panel. Nobody else does.

To find what needs looking at, start from the Dashboard: New, not yet triaged lists every open ticket you haven’t touched yet, most voted first, each with Triage.

The panel has three choices:

  • Status: one of the seven. See Statuses.
  • Type: Bug or Feature.
  • App: any app, including ones that aren’t taking new tickets or are archived.

Change what you need and select Save. Every change is stamped on the ticket’s timeline, so nobody has to wonder why it moved: changed the status, made this a bug or made this a feature request, and moved this from one app to another.

Followers are told about a status change, in their inbox and by email as they’ve chosen. Changes of type or app tell nobody.

A status change on its own often isn’t enough. Add a comment to say why, especially for Won’t fix, whose notice tells readers the reason is in your last comment. If you comment and change the status straight after one another, followers get the two as one notification and one email.

Set a ticket to Needs info when you need more from the person who filed it, and ask your question in a comment. The ticket’s notice says you need more information from them and that the question is in the last comment.

The person who filed it is told the question in their inbox and, unless they’ve chosen never to get email, by email straight away, even if they otherwise get a daily or weekly summary. When they reply on the ticket, it goes back to Open by itself, stamped on the timeline as their change. It doesn’t go back under Not yet triaged, because you’ve already touched it, but if you follow the ticket you’re told when it changes. Commenting follows a ticket, unless you’ve switched that off.

The dashboard’s Needs info count shows how many tickets are waiting on the people who filed them.

When two tickets are the same thing, mark the newer one as a duplicate of the other:

  1. On the duplicate, set Status to Duplicate.
  2. Duplicate of appears. Enter the other ticket’s number, such as FRG-148.
  3. Select Save.

Marking a duplicate merges it into the original:

  • Its votes and followers move to the original. Anyone who was on both is counted once.
  • The original’s timeline says you merged it into this, and how many votes came with it.
  • The duplicate is closed. Its vote box points to where its votes went, its notice sends readers to the original, and its comments are closed to everyone but you.
  • Everyone who followed the duplicate is told it’s been merged, and that they now follow the original.

If the ticket you name is itself a duplicate, the merge goes to the ticket that one was merged into, so votes never land on a closed duplicate. A ticket can’t be a duplicate of itself: the panel says Say which ticket this duplicates, as FRG and its number. It can’t be this one.

If a merge was a mistake, set the duplicate’s Status to anything other than Duplicate and select Save. Everything it had comes back: its votes and its followers. The original keeps only the votes and followers it had before the merge, so someone who voted on both keeps both votes. The original’s timeline says you split it back out, and how many votes went back with it.

To point a duplicate at a different ticket, split it back out first, then mark it as a duplicate again.

You can edit the title and write-up of any ticket, not just your own, unless its app is archived. Select Edit on the ticket. See Editing your write-up. The timeline shows your name beside the edit.

To remove someone’s comment, choose Remove from its ⋯ menu. Forge asks Remove their comment? and reminds you that to deal with the person as well, you go to their page in Admin. Select Remove to confirm.

The words, and any screenshots that came with them, are gone for good, and a line saying Removed by the maintainer stays in their place, so the replies around it still make sense. To remove everything someone has written at once, for spam, see Managing one person.