I completely agree with some of these suggestions, but it doesn't need all of them. If you really need a heavily-customizable issue tracking system, you can do anything you want in Bugzilla or Jira.
Every checkbox, dropdown and mandatory field they add makes GitHub Issues less attractive to those who don't need it. Simplicity is a feature, and it's one that you sacrifice as you make your software more flexible.
I guess it depends who is logging issues. If I'm experiencing some bug that I need fixed and motivated enough to log an issue at all, I'm probably motivated enough to fill out a few more fields.
Google Code had stars in order to encourage people to +1 something without creating noise and then instead of +1 comments you got +1 comments AND people yelling at them for using it wrong.
I completely agree with some of these suggestions, but it doesn't need all of them. If you really need a heavily-customizable issue tracking system, you can do anything you want in Bugzilla or Jira.
Every checkbox, dropdown and mandatory field they add makes GitHub Issues less attractive to those who don't need it. Simplicity is a feature, and it's one that you sacrifice as you make your software more flexible.
I guess it depends who is logging issues. If I'm experiencing some bug that I need fixed and motivated enough to log an issue at all, I'm probably motivated enough to fill out a few more fields.
Especially the +1
Best github support thread ever : https://github.com/isaacs/github/issues/9 (scroll down)
I made a similar issue here: https://src.sourcegraph.com/issues-playground/.tracker/26
I don't think a +1 button would help.
Google Code had stars in order to encourage people to +1 something without creating noise and then instead of +1 comments you got +1 comments AND people yelling at them for using it wrong.
+1. Fix this.
me too