views:

211

answers:

3

I know, there were posts before here on SO before concerning issue or bug tracking systems, like this one, but the given answers point either to commercial systems or web-based systems, which both seem to be oversized for our needs.

What I am looking for is a non-commercial tool for a team of 3 to 4 developers, which can be used on an existing fileserver, without the need of installing additional server software like a C/S database or a web server.

Some things I expect from such a system:

  • allows to remember bugs (with a priority) and issues / ideas for new features (mostly without a priority)
  • description of the issue, perhaps some additional remarks
  • short info who entered the bug/issue entry
  • one or more tags allowing us to group or filter the list

Any suggestions?

EDIT: I should have said that, but we are using MS Windows clients, Visual Studio development, Tortoise SVN (the latter works fine without a subversion server). And yes, I am strict on "no server software", since all server based solutions I have seen so far seem much to oversized/heavy weighted/too-much-effort-to-be-worth-it. In fact, if no one has a better idea, we are going to use a spreadsheet, but I can't believe there are no ready-made, light weight solutions.

+1  A: 

Well, if your needs are indeed modest, an OpenOffice Calc spreadsheet fits the bill well enough. With so few people in the same LAN, it would be manageable, would get the job done and takes a couple of minutes to set up.

Tomislav Nakic-Alfirevic
or a Google Doc, or a FileMaker DB, or an Access db, or an Excel Spreadsheet...
Jweede
Google Doc is also a good suggestion (probably even better: available everywhere, versioning and search part of the package...), but the rest don't fit into the picture as 1) FileMaker, Access and Excel are commercial tools and 2) it does take some more effort to set things up with Access and FileMaker.
Tomislav Nakic-Alfirevic
Yes, I could set up my own spreadsheet or Access DB, but I don't want to reinvent the wheel if there is already a better solution out there. MS Office XP is already available, so Excel and Access solutions would be ok, as long as if the spreadsheet or Access DB itself is free.
Doc Brown
Well, there's not much to the spreadsheet setup. You just need to agree on where to put the .xls files and define the issue structure: issue short name, details, date of creation, status (open/resolved/parked/closed), priority (1-5), assigned to, effort (hours), billable (true/false), date of closure, comment. You could obviously extend the list of columns/attributes further, but I'd advise settling on a subset of important attributes and commiting yourselves to use them. I would also suggest using one file per project to reduce probability of concurrent access.
Tomislav Nakic-Alfirevic
+2  A: 

Artifacts should fit your needs. It keeps data in Subversion, no additional server is required. Integrated into Visual Studio. Not free but $49 is rather low price tag.

Fyodor Sheremetyev
+2  A: 

I like Ditz for this purpose; it is very light-weight and stores all data in the version control system. It is written in Ruby so installing on Windows should not be a problem.

Kasper Peeters
SO only allows me to accept one answer, so I accept yours, since it fits best to the requirements I gave. I will try it out soon. The other suggestions are fine, too.
Doc Brown