Slashdot Mirror

← Back to Stories (view on slashdot.org)

Best Integrated Issue-Tracker For Subversion?

Posted by timothy on from the good-subversives-use-samizdat dept.

JobSeeker writes "Now that subversion has merge tracking my boss wants to save money by dropping our expensive commercial solution. I've pretty much convinced myself that subversion can do the job. I like it. But what about integrated issue tracking? Version control without issue tracking is only half a solution. The TortoiseSVN docs say a little about bugzilla and not much else. What ready-to-play options (commercial or open source) exist for deploying subversion on commercial projects?"

22 of 99 comments (clear)

  1. trac by bizpile · · Score: 4, Informative

    trac + subversion works well.

    1. Re:trac by justhatched · · Score: 1, Informative

      trac + subversion works well.

      Yes it does, very minor issue with Trac + svn tho, it needs to be on same server or you need to frig about with svn replications for the integration to work nicely.

    2. Re:trac by Midnight+Warrior · · Score: 2, Informative

      We use JIRA at work. It costs money for commercial use, but it is really, really nice. Integration with Subversion is available as a plugin. The main product is http://www.atlassian.com/software/jira/.

    3. Re:trac by turbidostato · · Score: 5, Informative

      By the way, there's Redmine that seems trying to be to Trac what Subversion is to CVS (in that it clearly builds up on Trac experiencies trying to do it better). It is multiproject for one, but I really didn't have the time to play with it (what about user management integration with LDAP, ACLs, threaded tickets, mailbox management, etc.).

      That said, Redmine is based on RoR, so I really don't know what will happen when/if they find the limits of the framework (and on my environment it seems easier to find people with Python experience than Ruby). To me and by now, I'd enjoy if Redmine/Trac is the base for a sane competition between them.

      Back on topic, not exactly what it was asked but one of the best open source ticket tracking tools over there I think is OTRS (no SVN integration and Perl based, though).

    4. Re:trac by djcapelis · · Score: 2, Informative

      There's actually a good plugin for supporting dependencies. We used it on a past project with some success: http://trac-hacks.org/wiki/MasterTicketsPlugin

      --
      I touch computers in naughty places
    5. Re:trac by Jack9 · · Score: 2, Informative

      3) No real ACLs

      To clarify, there are no real ACLs for tickets.

      For ACL to source, you can use SVN perms via trac.ini, authz_module_name if your authz_file contains permissions which are project named. Some people like me, are sometimes found using (Apache) Location directives before figuring this out.

      (authz_file contains)
      [calc:/branches/calc/bug-142]
      harry = rw
      sally = r ...
      (trac.ini contains)
      authz_module_name = calc

      Trac now recognizes ACLs the same as SVN does.

      --

      Often wrong but never in doubt.
      I am Jack9.
      Everyone knows me.
    6. Re:trac by turbidostato · · Score: 2, Informative

      "For ACL to source, you can use SVN perms"

      Will this work on searchs or if you trac-link from a wiki page or ticket?

      Regarding ACLs, I'm afraid is an all or nothing bussines. Current status (while I didn't look at 0.11 yet) means we cannot have a "private" section for our developers (yes, I'm aware of the "private" egg, but it doesn't work -shows "private" results on search, for instance), or "private" comments on tickets, etc.

    7. Re:trac by Anonymous Coward · · Score: 1, Informative

      I have been using redmine for over half an year now and I highly recommend it. It does the job and doesn't get in the way. Trac does...

  2. Redmine by thegrassyknowl · · Score: 5, Informative

    We've been using Trac for a long time and it worked well.

    We since discovered Redmine which does about the same job, is themed prettier and seems to be a bit easier to use. All in all Trac and Redmine both do about the same things.

    Redmine has a built-in user management, which I'm taking advantage of in our SVN/Hg web server to authenticate users with (single sign on)

    Redmine also has support for multiple projects in one tracker, whereas trac needs multiple installs for multiple disjointed projects. The workflow manager in Redmine is also really easy to use; no dicking about writing python scripts to control your workflow.

    Redmine talks to Svn, Git, Mercurial, Bazzar and a couple of other source control tools, which is useful if you ever need to move on to those tools. Trac is pretty rooted on subversion, though it does have a Git plugin.

    Both are pretty easy to install, but I had Redmine up and running in about 4 minutes whereas it took a bit of messing about to get Trac running.

    Redmine also has the manager friendly theme (think that horrible facebook style) so managers will goo and gaa over it then sign off that it be implemented.

    --
    I drink to make other people interesting!
  3. Re:TortoiseSVN by thegrassyknowl · · Score: 2, Informative

    Tortise isn't an issue tracker, it's a front end to Subversion. The OP wants an issue tracker (Think Trac, Bugzilla, Redmine, etc) which is a different beast.

    --
    I drink to make other people interesting!
  4. Plenty by c · · Score: 4, Informative

    Off the top of my head, you've got Trac, CVSTrac, Redmine, Collaboa... Trac is pretty well established. CVSTrac (AKA SvnTrac when dealing with Subversion) is lean and mean and absurbdly quick to set up. Redmine is pretty new, but seems to have picked up a lot of good ideas. Collaboa looks nice, but development appears to have stagnated.

    There's plenty of others, though. Commercially, things like FogBugz also have Subversion integration. But it's not exactly hard to find all this out: http://en.wikipedia.org/wiki/Comparison_of_issue_tracking_systems

    Be aware that once you lock yourself into a combination of SCM and issue tracking system, migrating to another SCM is absolutely hellish. Hope you really, really like Subversion.

    [disclosure: I mostly maintain CVSTrac]

    c.

    --
    Log in or piss off.
  5. Sorry, I missread topic, try Mantis by ya+really · · Score: 2, Informative

    Tortise isn't an issue tracker, it's a front end to Subversion. The OP wants an issue tracker (Think Trac, Bugzilla, Redmine, etc) which is a different beast.

    Oh, I guess I missread, thanks for letting me know. In that case, I'd reccomend Mantis. You can directly integrate it into SVN if you want. Here's the tutorial I used to integrate them together

    1. Re:Sorry, I missread topic, try Mantis by thegrassyknowl · · Score: 2, Informative

      Mantis looks OK but I prefer something that doesn't need quite as much work to integrate :)

      Redmine and Trac both just accept a repository path and bam - integration. Redmine does a bit of a messy with the repo by reading all the changeset information the first time you connect it to the repo though; that can take a long time if it's a well-established repo.

      --
      I drink to make other people interesting!
  6. Re:trac - no ... by Anonymous Coward · · Score: 4, Informative

    trac is not the best solution. Trac is a one-install per product gig.. not something that'll allow you to version and actually track issues across multiple products and multiple environments and multiple subversion repositories... all at once.

    Also, the wiki isn't that good.. tons of other great options that are actually good to wiki on.

    Jira has a great subversion connector... Jira has its quirks that I hate.... and I'd choose bugzilla if it weren't for a job.. but, honestly, the few thousand dollars jira is.. completely worth it.

  7. Comment removed by account_deleted · · Score: 5, Informative

    Comment removed based on user account deletion

  8. Comment removed by account_deleted · · Score: 4, Informative

    Comment removed based on user account deletion

  9. Jira by far by zyrorl · · Score: 1, Informative

    Jira is by far the best, they have legendary support (really they do), and for non-open source products, its probably the best supported commercial product ever. It also has a really good community surrounding it, and by far the best interface. It's also not legendarily expensive. Very affordable from a company point of view. Excellent functionality, pretty much handles anything you throw at it.

  10. Subversion "has" merge tracking by Darkforge · · Score: 3, Informative

    I know I'm not answering your question, but you may be asking the wrong question. Subversion 1.5 "has" merge support, but you still can't do safe bi-directional merges. (Wherein you make a feature branch "foo", merge from trunk to foo, foo to trunk, trunk to foo, foo to trunk, etc.)

    Also, you can't safely merge from branch to branch (merging from "foo" to your production "2.x" branch, without passing through trunk).

    Here's the designer of SVN merge support discussing the problem:
    http://subversion.tigris.org/servlets/ReadMsg?listName=dev&msgNo=127570

    Unfortunately, if you want real merges in an open source project, you're stuck with the distributed source control systems like git, mercurial, darcs, etc. even if you don't need distributed features.

    But you may come to like distributed source control (many people do)... they have tools like "ticgit" that you may like better than some of the other svn-based tools out there.

    --

    When I moderate, I only use "-1, Overrated". That way, I never get meta-moderated!

  11. Bugzilla by onlau · · Score: 3, Informative

    You can use Bugzilla and Subversion using scmbug (http://freshmeat.net/projects/scmbug/). It's a set of scripts you use as svn hooks. Setting it up is not really user-friendly but once it's set, well... you don't have to touch it anymore.

    You can solve a bug using the following comment on a svn commit:

    bug 42: resolved fixed
    blablablablah (real comment)...

    BTW it works for other control and bug-tracking systems...

  12. Scarab by Anonymous Coward · · Score: 1, Informative

    Take a look at Scarab (http://scarab.tigris.org). Setting it up takes a bit of time, but it's very versatile.

  13. TrackStudio by Lars+Fosdal · · Score: 2, Informative

    I am a satisfied user of TrackStudio from http://www.trackstudio.com/ Web-based, affordable, very configurable, and with an easy to configure integration with SVN. You can use most major databases for backend. You can model any number of workflows and have custom fields per workflow, per project or per user. Very effective searching and filtering allowing custom views. Email notification, Digests, RSS, etc. It also has an extensive SOAP interface if you need do some custom integration. It still is a bit weak on the report side, but the next major release give us a proper report designer. Most importantly, they have great support and are very receptive to your requirements, adding features that are frequently requested and of general interest. http://www.trackstudio.com/documentation/35/html/frames.html

    --
    Lars F.
  14. Re:RT ! by onecheapgeek · · Score: 2, Informative

    http://search.cpan.org/dist/RT-Integration-SVN/