It gives us great pleasure to announce our integrated issue tracking system! On repository pages you’ll now see an “Issues” tab in the top menu. Here’s a quick rundown of the features:
- Deal with your issues just like you deal with email (fast, JavaScript interface)
- Create and apply labels to issues to assign to users or categorize
- Drag and drop issues to prioritize them
- Vote on issues that you want to see tackled
- Search, sort, and filter
- Close issues from commit messages
- Keyboard shortcuts
Watch this short video introduction to GitHub Issues and get started now!
Report Issues issues at http://github.com/defunkt/github-issues/issues
If you already use another issue tracker, you can disable Issues in the new “Features” section of your repository’s “Admin” tab.
My dream became true, thank you guys!
This is huge!
And it’ll get out of the way on projects that already use Lighthouse/Trac/etc.? Awesome guys. This is a real big win.
Any chance this is going to get an API? I’d consider using this, but only if could easily import all my lighthouse tickets.
Awesome addition, thanks a lot!
Sweeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeet. Finally.
Is it possible to assign issues to people? Also, is there anyway to import bugs from other issue trackers?
Plan on supporting migrating issues from another system into github’s system?
Very shiny!
Holy crap!
Amazing!
Fantastic work on creating an intuitive user interface.
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
Rock! Going to start using this for my concurrency toolkit for C (chergert/iris) right away!
Awesome! This is a pleasant surprise.
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 ^^)
That’s a great feature. It’s not going to replace Redmine for me but it would be really nice for smaller projects.
very nice work guys! i really like the gmail style interface and shortcuts…
BAD. ASS.
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.
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: http://en.deadbeaf.org/2009/04/17/ditz-on-github-page/
That’s awesome! Keep up the good work!
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.
@ionfish GFM will only be used for message-type things. The readme’s will be unaffected.
wow
iirc markdown inserts tags in paragraphs if you add two or more spaces at the end of a line before the line break.
Awesome really! Now me at least only missing “project discussion board” in some flavour. Google Groups used mostly nowdays really really suck.
Thanks Tom, that’s reassuring.
Wow. Awesome. I’d hoped for this but didn’t think it would happen. Well done.
Man, I love it. Finally. The only feature I’ve been missing!
awesome.
Along with the API stuff, I would love to see the issues be saved right into the git project like ticgit:http://github.com/schacon/ticgit/tree/master does
Awesome! Well done
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.
Hurray!! But please please please also provide an API!
Very nice!!!
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.
@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.
wow, this is great. i’m loving it already and i haven’t even tried it out yet :D
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.
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! :)
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”
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.
Been hoping for this! GitHub ftw as usual!
Closing issues via commit can only be done by collaborators, so you shouldn’t have accidental closings.
Now let’s see how it handles spam.
How about attachments? And specifying what module. Nice start.
Ubercool! Keep up awesome work!
freakin’ awesome. Great job!
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.
Nice work!
Awesome! This is just what I wanted!
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?
@kieranp, if you go into the project’s ‘admin’ tab, you can disable the issues feature altogether.
Very nice!
This is awesome!
This is perfect!
Great job done boys!
Very nice, great work guys
If I write a comment in Russian then comment don’t post with a message “Comment must not be empty”.
Yay! Finally!
You guys rock :)
Absolutely awesome! This will be really useful. Thanks.
Nice. This is a big deal!
How does it work with branches? Will an issue be close if a fix is pussed to any branch or just the master branch?
Great work. Thanks!
Excellent! This is what I’ve been waiting for; goodbye Google Code, hello GitHub!
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.
Yes! Thank you so much for this!
How does this work with forks of a project (or does it work at all with forks of a project)?
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!
(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!
(aargh!)
Very curious about the details from issues across the various dimensions of git/github. Everything like such as:
All that aside, this is clearly a great addition!
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.
=D
Lighthouse killer, you just need a get-satisfaction app
@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:
http://github.com/defunkt/github-issues/issues/#issue/85
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.
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!
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 :)
This is very nice guys. I look forward to using this on upcoming projects.
Great feature, thanks!
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.
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.
Thanks, it’s very nice!
Will we see a speed increase? It renders pretty slowly on my netbook. Just wondering..
Holy smokes!
Is there a way to upload files? Patches, screenshots, etc.
very impressive… We will use it for sure
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 :-)
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: http://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?
rejoice… finally…
Hello,
I’ve written a script that allows you to migrate your tickets from Lighthouse to Github using the API : http://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.
The Issues tag is missing on the wiki subdomain. Will there be atom feeds? Great stuff this, by the way.
Hey,
The Github API has been updated, it now allows to add comments to issues.
I've updated my script. It also specifies the number of attachment of
the original LH ticket.
Read here for the list of changes :
http://suitmymind.com/2009/04/18/move-your-tickets-from-lighthouse-to-github/#update
Feel free to comment/patch/report issues, ...
Cheers,
Thomas.
Hello, I entered a request for Mylyn connector to the new GitHub issue tracker:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=272812
Let's see how many think that's a good idea.
Mike
This is great! Are there any plans to integrate additional project management tools into GitHub? We would like to stop using BananaScrum and/or ScrumNinja.
Awesome!
This is a great addition, thanks thanks thanks!
Thanks. Now I won't have to go to LH. :)
Looks interesting. But shouldn't you swap the "Open" and "Unread" workflow? ie. issues are initially "unread" until they are classified as "open" (maybe auto-classified when one of the project members read them).
oops, just found where I should have submitted that as an issue, so I did: http://github.com/defunkt/github-issues/issues/#issue/136
This bug has to be fixed.
http://github.com/defunkt/github-issues/issues/#issue/101
Otherwise minutes 2:32 is misleading! :P
awesome!
Really awesome, its amazing simply. Helpful a lot and many of my web design projects will complete for this effort.
Nice effort and great work done.
Excellent. I'll use this over the google code issue trackers, as my svn repos in non-google code projects will be pushed into github.
This is a great idea, i especially like the drag and drop prioritization.
this is a great article! fotografia ślubna and fotograf ślubny Bielsko
GREAT!. That sound like interesting.
http://www.bestrothira.info | http://moneyloanguide.blogspot.com
This is awesome, thanks for sharing info best toaster
the features that its offering are great and very useful.
okazii | bani pe net