[Trac] Feature comparison of Trac to Jira? (not baiting)

[Matthew Good]

On Thu, 2005-07-28 at 17:39 -0700, Jason Dunham wrote:
> I'm trying to install the beta and try to add this "custom" workflow in 
> our copy, but I don't understand the resistance into adding this into 
> Trac, or the assertion that the existing workflow is "good" enough for 
> most teams.  Doesn't everyone have this problem? 

If everyone had this problem then no one would be using Trac ;)  There
are many projects such as Trac itself and probably most of the
open-source projects using it that do not have a formal QA process, so
this is unnecessary.  At my office the projects that need it have worked
around the missing QA phase by providing a custom field for this
information.

I don't think that there's been any resistance from the development team
to allowing users to extend the workflow.  There has been a lot of work
on Trac's underlying architecture for 0.9 to make it more modular and
allow for many new ways for users to extend Trac with plugins rather
than patching the code.  While the workflow has not yet been modularized
that does not mean that it won't be.  

I think that allowing for a flexible workflow system is a very good
idea, although I'm hoping that some portions of the previously submitted
patches like the component QA owner and Milestone owner can be kept
separate from the mainline Trac code and we can start off with a basic
API to provide the necessary hooks for creating a workflow plugin.  

-- 
Matthew Good <trac at matt-good.net>