GitHub: Reorder issues in a milestone
11–20 of 33 posts
Re: GitHub: Reorder issues in a milestone
#12This is great. I thought this would be a useful feature at one point, and then just figured it would probably never happen. 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'd be great to collaborate where some people use Asana, some people use Trello, and some people just use textfile…
> I thought this would be a useful feature at one point You used to be able to do this ages ago. Reordering was one of the features that "no one used" and didn't make the cut when they rewrote "Issues 2.0" five years ago: https://github.com/blog/831-issues-2-0-the-next-generation
Re: GitHub: Reorder issues in a milestone
#13Re: GitHub: Reorder issues in a milestone
#14The 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.
It inspires one to wonder... what were they doing before that? Alternatively, perhaps they just hired a bunch of new people right then?
Re: GitHub: Reorder issues in a milestone
#15Unrelated 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).
Re: GitHub: Reorder issues in a milestone
#16Github gets on the front with re-ordering issues ;)
Re: GitHub: Reorder issues in a milestone
#17Unrelated 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).
Re: GitHub: Reorder issues in a milestone
#18Sorry, 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.
Re: GitHub: Reorder issues in a milestone
#19Can someone from GitHub explain why they removed it a few years ago [1], and why they changed their mind and added it back today?
[1] https://github.com/blog/831-issues-2-0-the-next-generation
Re: GitHub: Reorder issues in a milestone
#20The 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.
It inspires one to wonder... what were they doing before that? Alternatively, perhaps they just hired a bunch of new people right then?