I support some folks who I've gotten into using Trac for feature requests, issue tracking, etc. We have historically gathered requirement in spreadsheets or similar, collecting features, importance (mandatory, preferred, optional), relevant SW component, target version, etc. It seems to me that I could use Trac to more effectively collect, document, and track progress on Requirements.
I was planning on a new ticket Type of "requirement", and a priority of "mandatory", "preferred", "optional", then a component for each of our SW subsystems. Reuse the Milestone for target versions. Assign to developers as normal. Text fields in tickets would allow us to describe the high-level goal in the ticket subject, and we could provide rationale, use cases, and progress notes as normal. Seems like it would be a good fit. Are any of you using it for Requirements? Any words of wisdom? Things that work really well? things that didn't work for you? Thanks. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
