GitHub: Reorder issues in a milestone

Sorry, but it almost seems like some weird variation of Stockholm Syndrome that people get excited about this. It is a trivial feature that should have already been there, and was actually there over 5 years ago before they removed it. If you want to feature compare, Issues is still way behind what various other issue trackers had many years ago.

Unrelated feature request (because I bet people from GitHub are reading this thread): I'd love to be able to create gists under an organization account rather than attached to my personal profile (and hence only visible to members of that organization).

I&#x27;m amazed that a trivial feature addition like this can make the front page of HN.<p>GitHub may not be perfect, but they are clearly doing something right to win (or re-win?) the affection of the community.

Some people can&#x27;t make the front with a webapp that takes 3 months to create.<p>Github gets on the front with re-ordering issues ;)

The letter that the group of developers wrote a few months ago must have scared them, because they have been adding quite a few features compared to what they did the previous couple of years.

This is great. I thought this would be a useful feature at one point, and then just figured it would probably never happen.<p>Funny how any stream of notifications just turns into a todo list though. I wish I could just pipe them all to one place and have the changes actually committed back to the source. It&#x27;d be great to collaborate where some people use Asana, some people use Trello, and some people just use textfiles but they&#x27;re all in sync and it doesn&#x27;t matter where or how you make edits.

I love a lot of the changes github has been making. One sorely needed thing they&#x27;ve recently added is ability to assign issues to more than one person.<p>The one thing I am dying for is the ability to mark notifications unread. Notifications are a wonderful interface to catch up on things where you&#x27;re mentioned or needed, but there is no way to mark them as unread, so you have to deal with them right that second.

I&#x27;m happy they added back this feature.<p>Can someone from GitHub explain why they removed it a few years ago [1], and why they changed their mind and added it back today?<p>[1] <a href="https:&#x2F;&#x2F;github.com&#x2F;blog&#x2F;831-issues-2-0-the-next-generation" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;blog&#x2F;831-issues-2-0-the-next-generation</a>

Can some of the people who upvoted this explain why is this relevant?

The main issue I had with milestones is that you could not rename them. Have they fixed that one too?

Why not a general priority system? Why only for a milestone?