Github, how Not to release a new version

Github, how NOT to release a new version

https://github.com/blog/831-issues-2-0-the-next-generation

github released a new version of their issue tracking. They decided to eliminate the capability to prioritize and order issues with no advance warning because only "10" people used it. Everyone who had all our issues ordered lost the ordering. Their response? A big F*ck you because no one used the feature anyway. Thanks github!

Ok, so maybe Im smoking crack, but did you use the prioritization feature?

4 comments

[ 0.59 ms ] story [ 14.5 ms ] thread

bcx 15y ago ↗

We used the prioritization feature. Wow, I just noticed it on the website. That's a pain. Maybe we'll have to move back to pivotal tracker.

kneath 15y ago ↗

As mentioned earlier, the data is in our API and freely exportable (no loss of data). If you don't want to deal with the API – please contact support and we'll be happy to export the list of issues in order for you.

Alternately, you can use one of the many 3rd party applications that use our API such as http://githubissues.heroku.com/

bmelton 15y ago ↗

If 10 was the actual number, I find that hard to believe, since we have 3 in this thread so far (triviatise, bcx, myself).

storborg 15y ago ↗

My company used it too. Honestly, I can't imagine people not using it, particularly since there's no way to hide low-priority issues otherwise.

The new interface is somewhat frustrating in this respect because there is now no way to hide low-priority stuff at all. It would be nice if you could show all issues sorted by milestone due date, or anything to that effect. It's made even more frustrating by the fact that you can't seem to change the number of issues shown per page.