Hacker News new | ask | show | jobs
by pbowyer 3814 days ago
> The GitHub issue tracker does need to change.

Does anyone like any bugtracker?

That's a serious question. I've never used one that was a joy to use as a submitter (GH's issue tracker is one of the better ones, as it's so simple) or as a maintainer. As a maintainer I've found them really frustrating in general; JIRA has been one of the better ones for me.

Any consensus on 'decent' trackers?
1 comments
gkya 3814 days ago
> I've never used [a bug tracker] that was a joy to use as a submitter [...]

And it shouldn't be. If it is, people submit stupid bugs. When you get a notification of a bug, and you go read the bug, and try to reproduce it, you'll spend at least about five-ten minutes. The submitter then is obliged to spend at least about that much to report a proper bug report to an open source project where even the licence revokes the responsibility of the maintainer to respond to the submitter. And if good will and conventions can't force this, the bug tracker should.

link
pbowyer 3813 days ago
> And it shouldn't be. If it is, people submit stupid bugs.

I strongly disagree. You're conflating easy to enter a bug with a pleasure to use. There's no reason to throw both out.

Also, you're thinking of a public tracker. Where it's used within a team, having it easy and a joy to report issues is hugely beneficial, so they get logged without nagging and moaning.

link
chris_wot 3814 days ago
A repro steps field is a must. If I was a contributor (and I am!) then I would look at the thousands of bugs coming through and focus on only those with those that have that filled in.
link