On Tue, Apr 11, 2006 at 08:42:04PM +0200, solo turn wrote: > 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. >
If you have the Python skills available, I'd take a look at the workflow sandbox branch [1]. It specifically allows for custom fields with extra logic behind them. Here's an example plugin: http://swapoff.org/files/tracticketmojo-0.2.tar.gz Alec [1] http://projects.edgewall.com/trac/wiki/WorkFlow -- Evolution: Taking care of those too stupid to take care of themselves. _______________________________________________ Trac mailing list [email protected] http://lists.edgewall.com/mailman/listinfo/trac
