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. 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?
...
http://projects.edgewall.com/trac/ticket/886
I've added a comment.
The minimal implementation (to allow migrations) would be:
a) Provide the "Depends On" field (read/write)
b) Provide the "Blocks" field (read-only)
-
A simple extension:
the "close ticket" function would verify if the "depends-on" entries are
closed. if not, resolving the ticket as "fixed" will not be possible.
(this implementation can be later provided by an implemented workflow
mechnism)
.
--
http://lazaridis.com
_______________________________________________
Trac mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac
