Comments

• redchrom 1 day later

  My dream became true, thank you guys!

• rmm5t 1 day later

  This is huge!

• JackDanger 1 day later

  And it’ll get out of the way on projects that already use Lighthouse/Trac/etc.? Awesome guys. This is a real big win.

• dchelimsky 1 day later

  Any chance this is going to get an API? I’d consider using this, but only if could easily import all my lighthouse tickets.

• m5h 1 day later

  Awesome addition, thanks a lot!

• damog 1 day later

  Sweeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeet. Finally.

• 280north 1 day later

  Is it possible to assign issues to people? Also, is there anyway to import bugs from other issue trackers?

• thwarted 1 day later

  Plan on supporting migrating issues from another system into github’s system?

• drnic 1 day later

  Very shiny!

• spicyj 1 day later

  Holy crap!

• tchandy 1 day later

  Amazing!

• Odaeus 1 day later

  Fantastic work on creating an intuitive user interface.

• bjeanes 1 day later

  This is very much win. GMail interface plagiarising ftw!

  I saw the CSS for the issues tracker in the GH stylesheets a few days ago and got a bit excited

• chergert 1 day later

  Rock! Going to start using this for my concurrency toolkit for C (chergert/iris) right away!

• robolson 1 day later

  Awesome! This is a pleasant surprise.

• Youx 1 day later

  Wow, this is seriously awesome guys, just add support for assigning issues to people and it will fit most people’s basic needs! Thanks soooo much (though I have to say the interface has some kind of déja-vu feel hehe ^^)

• edavis10 1 day later

  That’s a great feature. It’s not going to replace Redmine for me but it would be really nice for smaller projects.

• jzting 1 day later

  very nice work guys! i really like the gmail style interface and shortcuts…

• zapnap 1 day later

  BAD. ASS.

• zapnap 1 day later

  I do wish that issues were saved/serialized in a branch of the project though, so that maybe a command-line issue tracker or something could integrate with them (see: ditz, git-issues). But as it is, this is swank.

• defunkt 1 day later

  zapnap: We may add that in the future, but you lose a lot of functionality by storing tickets in Git. And there’s always Ditz: https://en.deadbeaf.org/2009/04/17/ditz-on-github-page/

• davidwparker 1 day later

  That’s awesome! Keep up the good work!

• ionfish 1 day later

  I noticed a link to GitHub Flavored Markdown on the issue tracker, and have some qualms about your decision to break from the standard Markdown interpretation of newlines. I have a number of READMEs formatted with Markdown, hard-wrapped to 80 characters per line. Right now, GitHub happily turns those into paragraphs, but if I understand the GFM page correctly, this behaviour will be changing fairly soon. I would rather not reformat all my README files. Obviously not being able to use linebreaks is a limitation of Markdown, and I can understand the desire to resolve that, but I would prefer it if you could find another way to do so.

• mojombo 1 day later

  @ionfish GFM will only be used for message-type things. The readme’s will be unaffected.

• grimen 1 day later

  wow

• freels 1 day later

  iirc markdown inserts tags in paragraphs if you add two or more spaces at the end of a line before the line break.

• grimen 1 day later

  Awesome really! Now me at least only missing “project discussion board” in some flavour. Google Groups used mostly nowdays really really suck.

• ionfish 1 day later

  Thanks Tom, that’s reassuring.

• galenking 1 day later

  Wow. Awesome. I’d hoped for this but didn’t think it would happen. Well done.

• radekg 1 day later

  Man, I love it. Finally. The only feature I’ve been missing!

• pope 1 day later

  awesome.

  Along with the API stuff, I would love to see the issues be saved right into the git project like ticgit:https://github.com/schacon/ticgit/tree/master does

• juretta 1 day later

  Awesome! Well done

• garrytan 1 day later

  congrats guys, very well done!

  I’d love to see email integration or at least some hooks for someone to write some open source that would take care of that piece, perhaps through some form of web hooks api.

  I just want to be able to assign to people and know they got an email regarding it.

• tcurdt 1 day later

  Hurray!! But please please please also provide an API!

• ozeias 1 day later

  Very nice!!!

• rpheath 1 day later

  defunkt: how was it writing the javascript? (I believe you’re the javascript guru on the team, or at least, the one who loves it the most)

  Either way, awesome, awesome upgrade.

• defunkt 1 day later

  @rpheath: mojombo, pjhyett, and I all wrote JS for Issues. There are a lot of things I don’t like about the architecture of it – maybe if we refactor it in the future there will be a blog post about the adventure.

  Either way, I love working with JavaScript and jQuery.

• bakkdoor 1 day later

  wow, this is great. i’m loving it already and i haven’t even tried it out yet :D

• joshuabaer 1 day later

  That’s awesome – we were just about to start evaluating alternative solutions to Fogbugz. The only thing I see missing here that is very useful is the ability to include images or files with issues.

• moorage 1 day later

  This is fantastic news. Thanks!

  Also – does anyone else hear the similarities in the way mojombo talks/presents and how Steve Jobs talks/presents? Awesome! :)

• dinoboff 1 day later

  Can a commit to a fork update an issue opened on the main repository, like add a comment with the commit message and a link to the commit?

  Also, if a fork needs its own issue tracker there should be a way to know which issue “gh-1” in a commit message refers to; if the issue is on joe’s fork’s issue tracker, the message should be “fixes joe/gh-1”

• sanity 1 day later

  Looks interesting. Some suggestions (not all original):

  - An API so that people can write importers from their existing issue trackers - Extra points if you provide import scripts for popular issue trackers like Mantis

  Additionally: I’m not sure how powerful the search is, but this is a use case I had once with Trac and it was incredibly useful for project planning:

  I added a “time estimate” field to each ticket, the estimates were coarse, 2 hours, 1 day, 3 days, 2 weeks – something like that.

  I then created a report which could show, for each developer, the total time on their open tickets.

  If this issue tracker could support something like that, I’d be on-board in a new york second.

• thenduks 1 day later

  Been hoping for this! GitHub ftw as usual!

• defunkt 1 day later

  Closing issues via commit can only be done by collaborators, so you shouldn’t have accidental closings.

• Pistos 1 day later

  Now let’s see how it handles spam.

• ianlevesque 1 day later

  How about attachments? And specifying what module. Nice start.

• darwin 1 day later

  Ubercool! Keep up awesome work!

• glie 1 day later

  freakin’ awesome. Great job!

• brandonh 1 day later

  awesome.

  honestly, i think you should charge for all accounts that write.

  the internet needs a new model and everything github does is worth seven bucks.

• DylanFM 1 day later

  Nice work!

• dvyjones 1 day later

  Awesome! This is just what I wanted!

• KieranP 1 day later

  The issues feature looks great, but we already have an established system. We would like to direct users to that instead. Is there a way that same link could be set to our external tracker?

• brandonh 1 day later

  @kieranp, if you go into the project’s ‘admin’ tab, you can disable the issues feature altogether.

• gbarnett 1 day later

  Just what GH neededm thanks!

• btakita 1 day later

  Very nice!

• bleeder 1 day later

  This is awesome!

• unders 1 day later

  This is perfect!

• peterz 1 day later

  Great job done boys!

• adulteratedjedi 1 day later

  Very nice, great work guys

• meritt 1 day later

  If I write a comment in Russian then comment don’t post with a message “Comment must not be empty”.

• Tobbe 1 day later

  Yay! Finally!

  You guys rock :)

• garyhodgson 1 day later

  Absolutely awesome! This will be really useful. Thanks.

• bowsersenior 1 day later

  Nice. This is a big deal!

• jnicklas 1 day later

  How does it work with branches? Will an issue be close if a fix is pussed to any branch or just the master branch?

• koraktor 1 day later

  Great work. Thanks!

• philbooth 1 day later

  Excellent! This is what I’ve been waiting for; goodbye Google Code, hello GitHub!

• awendt 1 day later

  Somehow I’ve known this would happen eventually, and it’s a good thing at first glance. But it doesn’t play well with git’s decentralized nature.

  Everything else you’ve offered so far is not tied to Github: Once I’ve cloned the repo, graphs and source browsing can be done anywhere. Heck, even pages are stored in a repo I can clone!

  If you guys would put issues into a branch or something, that would be just fair. Otherwise, this would be a major lock-in.

• rnavarro 1 day later

  Yes! Thank you so much for this!

• kballard 1 day later

  How does this work with forks of a project (or does it work at all with forks of a project)?

• charlieok 1 day later

  Very curious about the details from issues across the various dimensions of git/github. Everything like such as:

  A project with multiple forked repositories Branches within a repository webhooks in and out for creating/closing/other operations

  All that aside, this is clearly a great addition!

• charlieok 1 day later

  (again, with markup this time)

  Very curious about the details from issues across the various dimensions of git/github. Everything like such as:

  A project with multiple forked repositories Branches within a repository webhooks in and out for creating/closing/other operations

  All that aside, this is clearly a great addition!

• charlieok 1 day later

  (aargh!)

  Very curious about the details from issues across the various dimensions of git/github. Everything like such as:

  • A project with multiple forked repositories
  • Branches within a repository
  • webhooks in and out for creating/closing/other operations

  All that aside, this is clearly a great addition!

• bleeder 1 day later

  Is there an API available for this issue tracker? It’s very nice to work with so far by the way, very intuitive and Gmail-esque.

• andion 1 day later

  =D

• marze 1 day later

  Lighthouse killer, you just need a get-satisfaction app

• dinoboff 1 day later

  @defunkt I am not worried about accidental closing. I would like my fixes on my forks to be linked to issue on main project issue tracker:

  https://github.com/defunkt/github-issues/issues/#issue/85

• astro 1 day later

  I’d love interoperability with ditz, which btw would circumvent the need for an API. Also, it ensures data portability, which is the matter that makes GitHub my favourite social network because my repository stays mine.

• mwilliams 1 day later

  I didn’t have a chance to go through all of these comments, but, I think it would be a great idea if I could also label an issue from a commit message.

  We often used a “resolved” tag for our issues that have been completed and once the code has been reviewed, we then close them. So we if could do a commit message like “resolved-1” and it would then tag that issue with that specific label.

  But great work so far! Awesome work!

• eviltrout 1 day later

  I am incredibly excited for this. Lighthouse has been taking forever to implement a batch update feature and you guys have it in your first release. I will be switching the second you release the API for it :)

• digitaltoad 1 day later

  This is very nice guys. I look forward to using this on upcoming projects.

• gmosx 1 day later

  Great feature, thanks!

• PEZ 2 days later

  Indeed, great job. I’ve created my first issue and it was even fun! =)

  Please give it an API. I want to connect Mylyn (in Eclipse) to it. I can’t function without Mylyn.

• secelis 2 days later

  Don’t allow anyone to assign an issue to anyone. But do allow people to assign themselves to an issue. I don’t want anyone to hand me work to do, even if it’s on my own project.

• zpmorgan 2 days later

  Thanks, it’s very nice! Will we see a speed increase? It renders pretty slowly on my netbook. Just wondering..

• jettero 2 days later

  Holy smokes!

• bentlegen 2 days later

  Is there a way to upload files? Patches, screenshots, etc.

• otaviofcs 2 days later

  very impressive… We will use it for sure

• liyanage 3 days later

  Awesome, this is exactly what I was hoping for! And more thanks for using the j/k keyboard shortcuts… I love it whenever someone gets that right :-)

• kris 3 days later

  Glad you added support for issue tracking, I was just speaking to my boss about how much I’d love this.

  I wrote a post about it: https://www.mrkris.com/2009/04/18/github-issue-tracking/

  To summarize, features I would like to see, personally, before I ditch BaseCamp and LightHouse:

  1. Attachment support 2. Instead of creating a label for people to assign to, why not pull from contributor list instead? 3. Why the sort-based priorities?

• devniv 3 days later

  rejoice… finally…

• suitmymind 3 days later

  Hello,

  I’ve written a script that allows you to migrate your tickets from Lighthouse to Github using the API : https://suitmymind.com/2009/04/18/move-your-tickets-from-lighthouse-to-github/

  The script is surely not perfect, but I hope I can improve it with your feedback.

  Best, Thomas Balthazar.

• dag 3 days later

  The Issues tag is missing on the wiki subdomain. Will there be atom feeds? Great stuff this, by the way.

Participate