Re:GitHub Raises $250M at $2B Valuation
by mpdehaan2 on Thursday July 30, 2015 @12:56PM
(#9976293)
I'm not positive they use it for issue tracking but they may. In my case, I was dealing with a single repo with 1000 or so contributors, and they were community people so it was very hard to get them to file quality structured bug reports, and the system didn't really allow for asking questions.
It lacks strong organizational features, categorization, issue templates, search, and ability to save filters.
I've seen a lot of projects use it for pull requests and then disable the issue tracker, which is good and bad - you get a better tracker, you miss probably half of the bug reports.
Re:GitHub Raises $250M at $2B Valuation
by mpdehaan2 on Thursday July 30, 2015 @07:13PM
(#9978873)
They can be applied by the owner, but I guess I was thinking more of the ability to have a required 'component' field or a required field for the type of the ticket.
It lacks strong organizational features, categorization, issue templates, search, and ability to save filters.
I've seen a lot of projects use it for pull requests and then disable the issue tracker, which is good and bad - you get a better tracker, you miss probably half of the bug reports.