Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitHub: Reorder issues in a milestone

github.com

Post reply on HN
Print view View original

1–10 of 33 posts

Re: GitHub: Reorder issues in a milestone

#4

Post by diziet »

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.

Re: GitHub: Reorder issues in a milestone

#5

Post by sytse »

diziet wrote: post #4

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.

BTW We're working on ordering issues as part of an issue board https://gitlab.com/gitlab-org/gitlab-ce/issues/17907

Re: GitHub: Reorder issues in a milestone

#6

Post by state »

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.

Re: GitHub: Reorder issues in a milestone

#7

Post by technomancy »

state wrote: post #6

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 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

#8

Post by jessaustin »

farresito wrote: post #3

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.

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

#9

Post by evv »

I'm amazed that a trivial feature addition like this can make the front page of HN.

GitHub may not be perfect, but they are clearly doing something right to win (or re-win?) the affection of the community.

Re: GitHub: Reorder issues in a milestone

#10

Post by dlandis »

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.
Post reply on HN