Jørn A Hansen wrote:
On 2/22/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
I've read a little within the trac wiki, but get confused of how the
status is.
Are there any methods to model ticket-dependencies (depends-on <-> blocks)?
I think that depends on the level of functionality you want. I imagine
the simplest possible solution to this is just adding a custom field
where you can reference the other tickets and then do searches based
on this.
(sorry for the late answer, is was off-line for a few days).
I would like to avoid custom fields for this essential functionality.
but: does trac provide migration capabilites for custom fields?
This would allow me to define 2 fields, which can be later migrated to
the standard fields (if provided).
Can you describe your requirements a bit further? Maybe you
can add something useful to the #886 ticket which is probably the one
describing this?
I have not yet defined personal requirements for this.
But the general requirements for trac would be:
a) enable simple migration from competitive tracking system
databases(e.g.bugzilla)
the resulting filed would be initially:
a) Depends On
b) Blocks
Possible Implementation Sequence:
a) provide the "Depends On" field
b) provide the "Blocks" field (read only)
c) provide automatism to update entries (Depends On => Blocks)
d) provide visualization of dependency tree
e) make "Blocks" field writable
c) provide automatism to update entries ( Blocks => Depends On)
Reading the wiki I can understand you gets confused. An old-ish
[...] - (additional information)
.
--
http://lazaridis.com
_______________________________________________
Trac mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac
