Another Zope Issue Tracker
I found this Issue Tracker yesterday while looking at ZWiki.org for ZWiki updates.
My quest for a good issue tracker is still frustrating. Tracker still comes closest to what I seem to want - something with detail and workflow for team use, but not too difficult for a non-tech person to submit an issue.
But I also like the simplicity of this bug tracker by Brent Simmons. I wonder if I might just end up writing my own that's closer to this.
Personally, I didn't mind Roundup as a bug tracker. It was fast, and the other developer and I that used it during the transition phase of 24Tix 1.0 were pretty succesful with it. But there were some things that I ultimately had too much issue with:
- No indication that a post-install schema change was possible. I wanted to add in a couple of fields, such as Expected Version and References, to an already running database. I know now that this is in fact doable.
- Configuration and setup of new instances too difficult. Actually, they've done a decent job of this, but really getting Roundup installed requires better Unix familiarity than I have - particularly things like setting up a dedicated Roundup user/group. I'm primarily a developer, not an administrator, and the guy who runs the administrator duties never had time to help me here. This could be a significant issue if I needed to go through him every time I needed to set up a new instance. In Zope, one just adds a new Tracker (Or CMF Collector, or IssueTracker, or what have you). It's a domain I'm personally more familiar with, so I'm going to stay there for the time being.
- Difficult to integrate with other Project artifacts. With Roundup, the issue tracking database was off in its own area, even when using ZRoundup (which is basically a small gateway between Zope and the normal Roundup CGI application). Thus, a few structural and navigational elements I was using in the look and feel of our very basic Projects site would get lost.
Basically, I've come to the conclusion that I'm too steeped in Zope for anything else to be useful on the time tables that I have. Tracker is nice now that it's running, but there are still small gotchas and rough areas.
Right now, our Project Management site is a loose collection of folders, letting the person responsible for a certain project to decide how they want to track artifacts. Most of my projects use a combination of ZWiki and Tracker, to some degree of success. It's lightweight and easy to get up and running for a new project, and I've had success with this combination before.
As things grow, however, real content management might be needed. Perhaps when CMF hits 1.3 and Plone hits 1.0, I'll reconsider CMF + CMFCollector. But the solution we have now works decently.