git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: choosing an issue tracker

From
Bill Lear <rael@zopyra.com>
Date
Dec 2, 2009, 11:54 UTC
Message-ID
<19222.21872.425947.273352@lisa.zopyra.com>
In-Reply-To
<4B16331A.3060606@gulfsat.mg>
On Wednesday, December 2, 2009 at 12:27:54 (+0300) Rakotomandimby Mihamina writes:
Show 19 quoted lines
>Hi all,
>
>For a while, I used SVN and Trac.
>They have a satisfying mutual integration.
>
>I am looking for our new issue tracker, and would like to be advised.
>
>Our context:
>- developpers using git, developping
>   - web based applications (PHP, Python, OCaml,...)
>   - Unix-like system maintainance scripts (SHELL, Perl,...)
>- a QA guy that makes functional tests only on the web applications
>   and reports bugs and potential improvements. He does not use git.
>- multiple projects
>
>What we look for:
>something like the (Trac, SVN) but with git as SCM.
>
>What issue tracker would you recommend?

You might be interested in Jira, which I have tied to git with my open-source niftyism:

http://github.com/rael/git-jira
Bill
Previous: Matthieu Moy
Message 3 of 3 in “choosing an issue tracker”
  1. Rakotomandimby MihaminaDec 2, 2009
  2. Matthieu MoyDec 2, 2009
  3. Bill LearDec 2, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.