Under the "<i>All the small things</i>" section of the post:<p>> "You'll get a notification if an issue is assigned to you."<p>> "No more mixing: the "issues" tab will only show you issues, and the pull requests tab will still only show pull requests..."<p>> "If you use Task Lists, we'll show the overall progress on that issue or pull request on the listing page: "<p>Yes! These are three features that I have been waiting on for awhile now. Especially now that I don't have to open a ton of tabs to see task lists for each issue. That's so awesome the task lists are now in the list UI.<p>Great work, GitHub!
This is nice. There are two things however that would make GitHub issues awesome:<p>1. Starring / Voting an issue. The count of stars/votes should be visible and we should have the ability to sort by the number of stars / votes.<p>2. Labels with values. Simple integers types would do to begin with. For example, priority:1, priority:2, etc. And then being able to sort by the value.
I'm still confused by the inability to do prioritisation. Why does Github so stubbornly not have a way of doing that including sorting on it? I am aware you can create arbitrary labels, but that doesn't help with sorting.<p>We long ago gave up on Github issues because of this, and use Trello instead where priority is simple drag and drop. The other problem is that you can't easily copy/move/link issues between repositories. This becomes necessary when you have different repos (eg a server one, an android one and a web one) and something is reported against the "wrong" repo. Not the reporters fault, and very tedious to correct.<p>This is all one area where Google Code does things so much better (yes you can prioritise and sort). Each project can have any number of repositories and they all share the same wiki and issue tracker. That is a lot easier to deal with. Of course refusing to take money, and apparently losing interest means it can't be used.
Is there a way to search by the status flags? It's now harder to see them since they're no longer in the same column, and I use the "has passed tests" filter frequently to check which PRs might need shepherding on Servo (<a href="https://github.com/servo/servo/pulls" rel="nofollow">https://github.com/servo/servo/pulls</a> )
I mostly like this, especially the way in which things like label/title changes are finally displayed.<p>You know what I would <i>really</i> like to see next? A bit of adaptive design. Something that will let me use a narrow viewport without needing to scroll back and forth all the time.
Two feature requests:<p>1. hiding issues<p>2. CC people / stop notification<p>For example as more and more teams are using Github, and although the spirit of open source is collobration, sometimes security bugs are probably better handled if they are hidden until resolved.<p>There are two ways to do this now:<p>* email<p>* bugzilla / bug bounty site<p>Wouldn't it be awesome if I could just let people report security bugs on Github except they are hidden as opposed to managing and tracking tickets from multiple places?<p>I know now you can CC people using @ but what about muting notification? As a bugzilla user, I can stop being notified if I remove myself from the CC list.
This is nice and everything, but the one thing that I don't like so far is that getting to the list of labels isn't just a sidebar away anymore but instead a whole tab change.
I do see that you can filter by label through the filter textbox, but that isn't quiet the same for someone like me who uses the colors more than the name of the label.<p>Overall, looks nice though. Curious to hear what power uses think of it.
One thing I noticed recently that really bit me was I created a few issues on a public repo which decided to disable issues and so I lost them forever.
I'd love support for an issues.markdown - which appears at the top of the issues list or above the form for creating a new issue. I have a moderately popular web app which it want to keep client side only but which gets constant requests to add saving / server side..
This is great! One thing that I was not able to find: is the activity tracking around labels exposed in the API? We (the Brackets team) actually wrote a tool to collect data about when a label was added or removed and it would be a welcome change to not have to support that :)
I seem to get a 500 error page whenever I search for something along the lines of "NOT label:css". I was hoping to be able to find issues that are not labeled as something.<p>Other than that this seems like a great improvement!
All great updates, but it's missing one key thing for us: the checklist tracking only includes check items from the first post on an issue thread. Any checklists in subsequent issue comments are not counted.