Hi Solo, I'm replying to your comment to the Trac list from Feb 20th about requirements management. I'm also using Trac for requirements, and I was wondering how you use the custom fields for dependencies...
Do you just have a single custom field that you enter other ticket IDs into? How do you handle multiple dependencies? Any way I could see a screenshot of what your's looks like --keeping in mind I don't want you to disclose intellectual property unnecessarily? Also, I was looking at the intertrac stuff, but don't see how this solves the dependencies problem. It looks like a way to link to different Trac projects. For the list, a couple of useful things that other requirements tools do is to be able to export as a word doc and the ability to order requirements in reports (of course this could be solved by a custom field, but I can see this becoming hard to manage if requirements change). Thanks for the assistance... Ashley Confidentiality Note: This email is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If the reader of this email message is not the intended recipient, or the employee or agent responsible for delivery of the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is prohibited. If you have received this email in error, please notify Jabber, Inc. immediately by telephone at +303-308-3231. _______________________________________________ Trac mailing list [email protected] http://lists.edgewall.com/mailman/listinfo/trac
