How Tam sorts the tracker

Labels

Tam is given the list of labels your repository has, with their descriptions. He picks up to three for a new issue, or none when none fits. A label that does not exist in your repository cannot be applied: the server checks every name against your list.

Duplicates

He is also given the titles of your other open issues. When a new issue reports the same thing as one of them and he is confident, the draft carries a short note pointing at the earlier issue and asking the author to say what differs if it is not the same.

Missing details

When a bug report cannot be reproduced from what was written, Tam asks for exactly what is missing: the version, the steps, what was expected and what happened. One message, no template dump.

What he never does

He does not close issues, assign people, create labels or change milestones. The app is not given a way to do those things from a draft.