On 2/24/06, Ashley Roach <[EMAIL PROTECTED]> wrote: > 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?
currently we don't use a dedicated field for it. if you enter #1 for example, it is displayed like that and not linked to anything else which is not good. so we put them in the text and have no possibility to track find them. but if we would use a field, we would use one field "depending on", which holds multiple tickets. > 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. you are right, intertrac is about how to link. you need something else for dependencies, one proposal is http://projects.edgewall.com/trac/wiki/TracCrossReferences. but i think you need both for a "distributed project world". -solo. _______________________________________________ Trac mailing list [email protected] http://lists.edgewall.com/mailman/listinfo/trac
