In the phabricator bug tracker there is a feature i like called tokens where users can award tokens to a bug (i guess its the same as github reacting to the bug, but i like how phab did the ui better). Lets users note that it is affecting them without derailing the conversation.
And it is useful to have a rough count of how many users are affected by a bug. Especially for the harder to reproduce ones where it is unclear if investigating is worth it.
Its not abusive to close duplicate reports of a bug that is not currently prioritized. It would be impossible to prioritize every single bug.
And then there’s the owner/company response to a trouble report: “nobody has reported this”
On the contrary those are helpful. It means the steps to reproduce are unclear or incomplete.
But often the key people responsible use that phrase as a shield to seemingly reject the suggestion that there is a problem.
I've experienced this so many times with ISPs over the years. I offer them a lot of details, but the most common initial (and final) response is "nobody else has reported this". Obviously the first person reporting a problem will be in this situation.
> But often the key people responsible use that phrase as a shield to seemingly reject the suggestion that there is a problem.
Have you ever been on the other side of this? If a single person reports that something sometimes doesn't work, they don't know under what circumstances it doesn't work or have any meaningful description on how to make it do the problematic thing, and nobody else is experiencing it - 9 times out of 10 its a problem with the reporter. Even if it isn't, the description of the problem is so vague and useless there's nothing to be done.