John, MOST of what you are talking about is currently possible via some of the plugins at Trac Hacks. Just google it, it'll show up as the first hit. If you need some assistance figuring out how to combine these plugins to get the desired capabilities, let me know. I can walk you through it.
-Chris On 6/27/07, John M Camara <[EMAIL PROTECTED]> wrote: > > My company is in the process of selecting tools for change and > requirements management. They initial were looking only at commercial > products but I have been pushing for an open source solution. I felt > that Subversion & Trac already handles at least 60% of the > requirements and customizing Trac and building a simple Requirements > Management system would cost close to what it would cost to buy the > commercial products. > > Areas in Trac that I see need to be worked on are: > > * creating a plugin to manage custom permissions with web interface > * permissions web page > * make it easier to use when large numbers of users exist > * separate forms for adding users and roles (just cosmetic nothing > would change in the back end) > * add a view for displaying roles vs users > * ticket > * multiple ticket types (subclasses of Ticket) > * support for ticket hierarchies (child tickets) by adding a > parentTicketID field > * ticket fields > * defining and modifying custom ticket fields through a gui > * custom fields get assigned to a ticket type > * define the work flow transitions in which fields are writable, > required, readonly > * work flow > * separate workflows for each type of ticket > * add a gui for defining and modifying ticket workflows > * SQLAlchemy migration > * and some additional template customizations > > Most of these changes are minor changes to Trac or simple plugins that > need to be created except for the SQLAlchemy migration. > > The largest piece of work required in my proposal would be to create a > requirements management system. This system would have to support > features like > > * Managing requirements for multiple requirement documents > * Traceability between requirements from within a requirements > document, to a requirement in another document, external references, > or to files in the repository > * Integration with Trac's ticket/workflow > * Management of different views of the requirements > * Version control of requirements > * managing requirement properties > * support for multiple requirement document types - i.e test case, > user requirements, etc > * support for multiple requirement types - i.e use case, functional > requirement, marketing, unit test, etc > * etc > > I have noticed lately that more and more large companies are starting > to adopt Trac so maybe some of you that are reading this would also be > interested in this development. If you have any interest in this > project let me know. Especially if your interested in doing some of > this development or if you company may be interest in sharing the cost > of some of the development. > > Any support from the community will greatly improve the chances that > my company will accept my proposal. If they do accept it they would > be willing to spend a reasonable amount of funding for this project > although I don't know the exact level at this time. This would be a > great opportunity for Trac to gain additional corporate users as well > adding some new features to Trac, especially completing the SQLAlchemy > migration. > > If my company accepts the project (decision to be made mid July) > development would be ramped up quickly as a beta would be expected by > the end of the year. > > John > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to trac-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
