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'm not sure if this is really a good thing. Possibly people are happy that some really annoying problem finally got fixed, rather than celebrate the feature itself. "GitHub stopped killing puppies" would also likely make a front page.
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.
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 textfiles but they're all in sync and it doesn't matter where or how you make edits.
> 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:
I love a lot of the changes github has been making. One sorely needed thing they've recently added is ability to assign issues to more than one person.
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'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 agree on having a need for that feature myself too. In GitLab we solved it by not marking TODO's when you read them but only when you take action. The problem has been when you don't want to do anything (reply, comment, vote, etc.). That is why we just added the ability to mark TODO's as read in GitLab in 8.9 https://about.gitlab.com/2016/06/22/gitlab-8-9-released/ section "Manually add Todos" (you can mark them done in the same spot.
The rationale I heard back then was "no one used it". My guess is that these days, even if "no one" means "less than 1% of users" it still amounts to hundreds of thousands of people.
Because a lot of people use github issues and milestones as a way to gauge what is needed to be done for what release, and the ability to order by priority is a great option.
You may think it's trivial and doesn't deserve the front page, but many people do. Clearly.
dlandis|9 years ago
ngrilly|9 years ago
simonw|9 years ago
andreynering|9 years ago
- https://github.com/dear-github/dear-github/issues
- https://github.com/isaacs/github/issues
moby|9 years ago
aserafini|9 years ago
Gmo|9 years ago
evv|9 years ago
GitHub may not be perfect, but they are clearly doing something right to win (or re-win?) the affection of the community.
viraptor|9 years ago
NicoJuicy|9 years ago
Github gets on the front with re-ordering issues ;)
farresito|9 years ago
jessaustin|9 years ago
state|9 years ago
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 textfiles but they're all in sync and it doesn't matter where or how you make edits.
technomancy|9 years ago
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
diziet|9 years ago
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're mentioned or needed, but there is no way to mark them as unread, so you have to deal with them right that second.
sytse|9 years ago
BTW We're working on ordering issues as part of an issue board https://gitlab.com/gitlab-org/gitlab-ce/issues/17907
ngrilly|9 years ago
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?
[1] https://github.com/blog/831-issues-2-0-the-next-generation
technomancy|9 years ago
guessmyname|9 years ago
joshmanders|9 years ago
You may think it's trivial and doesn't deserve the front page, but many people do. Clearly.
kingosticks|9 years ago
joshmanders|9 years ago
unknown|9 years ago
[deleted]
qznc|9 years ago