{"thread":{"id":"21822","subject":"choosing an issue tracker","startedAt":"2009-12-02T09:27:54Z","lastAt":"2009-12-02T11:54:24Z","messageCount":3,"participants":["Rakotomandimby Mihamina","Matthieu Moy","Bill Lear"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"128984","messageId":"4B16331A.3060606@gulfsat.mg","threadId":"21822","inReplyTo":null,"subject":"choosing an issue tracker","fromName":"Rakotomandimby Mihamina","fromEmail":"mihamina@gulfsat.mg","sentAt":"2009-12-02T09:27:54Z","receivedAt":"2009-12-02T09:27:54Z","isPatch":false,"sender":{"key":"mihamina@gulfsat.mg","avatar":null},"body":"Hi all,\n\nFor a while, I used SVN and Trac.\nThey have a satisfying mutual integration.\n\nI am looking for our new issue tracker, and would like to be advised.\n\nOur context:\n- developpers using git, developping\n   - web based applications (PHP, Python, OCaml,...)\n   - Unix-like system maintainance scripts (SHELL, Perl,...)\n- a QA guy that makes functional tests only on the web applications\n   and reports bugs and potential improvements. He does not use git.\n- multiple projects\n\nWhat we look for:\nsomething like the (Trac, SVN) but with git as SCM.\n\nWhat issue tracker would you recommend?\n\n-- \n       Architecte Informatique chez Blueline/Gulfsat:\n    Administration Systeme, Recherche & Developpement\n                                    +261 33 11 207 36\n"},{"id":"128987","messageId":"vpqeind90jy.fsf@bauges.imag.fr","threadId":"21822","inReplyTo":"4B16331A.3060606@gulfsat.mg","subject":"Re: choosing an issue tracker","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@grenoble-inp.fr","sentAt":"2009-12-02T09:40:01Z","receivedAt":"2009-12-02T09:40:01Z","isPatch":false,"sender":{"key":"matthieu.moy@grenoble-inp.fr","avatar":"https://gravatar.com/avatar/72c8a2705971a25dfaff23cece15130d405685845d911aedd5667ace277f3fc5?d=mp&s=160"},"body":"Rakotomandimby Mihamina <mihamina@gulfsat.mg> writes:\n\n> What we look for:\n> something like the (Trac, SVN) but with git as SCM.\n>\n> What issue tracker would you recommend?\n\nI couldn't recomand one, but the among the ones to look at:\n\nInDefero (clone of google code)\ntrac+git (I've been told it wasn't as good as trac+svn, but it exists)\n\n-- \nMatthieu Moy\nhttp://www-verimag.imag.fr/~moy/\n"},{"id":"128999","messageId":"19222.21872.425947.273352@lisa.zopyra.com","threadId":"21822","inReplyTo":"4B16331A.3060606@gulfsat.mg","subject":"Re: choosing an issue tracker","fromName":"Bill Lear","fromEmail":"rael@zopyra.com","sentAt":"2009-12-02T11:54:24Z","receivedAt":"2009-12-02T11:54:24Z","isPatch":false,"sender":{"key":"rael@zopyra.com","avatar":"https://gravatar.com/avatar/c4f2d2790ca3828d3b4e7dfebabf61d2fe94fd82fa49cdac2a5295dd2d46a874?d=mp&s=160"},"body":"On Wednesday, December 2, 2009 at 12:27:54 (+0300) Rakotomandimby Mihamina writes:\n>Hi all,\n>\n>For a while, I used SVN and Trac.\n>They have a satisfying mutual integration.\n>\n>I am looking for our new issue tracker, and would like to be advised.\n>\n>Our context:\n>- developpers using git, developping\n>   - web based applications (PHP, Python, OCaml,...)\n>   - Unix-like system maintainance scripts (SHELL, Perl,...)\n>- a QA guy that makes functional tests only on the web applications\n>   and reports bugs and potential improvements. He does not use git.\n>- multiple projects\n>\n>What we look for:\n>something like the (Trac, SVN) but with git as SCM.\n>\n>What issue tracker would you recommend?\n\nYou might be interested in Jira, which I have tied to git with my\nopen-source niftyism:\n\nhttp://github.com/rael/git-jira\n\n\nBill\n"}]}