On Wed, May 4, 2011 at 3:09 PM, Stephan Beal <[email protected]> wrote: > i thought maybe each child could be a separate fork, and then be changed in > its own branch of the hierarchy. i have no idea if it's feasible, though.
The parent-child between issues is not the same as between revisions of an object, which could be a ticket. Fossile does version tickets, but does not provide an interface for dealing with forks or branches. I have even looked at the timeline and history pages for a ticket and there is no indication of leaves. While it is easy enough to add fields to tickets, and easy enough to add a "Create Related Ticket" button on the View Ticket page, I don't think Fossil provides a way to pass user parameters to the New Ticket page. I think you would have to use Javascript to save the ticket's ID in a cookie on the View Ticket page, then more Javascript to fetch it from the cookie on the New Ticket page. Beyond creating child tickets, adding the ability to pass in user parameters to the New Ticket page could help make things like website error reporting and ticket generation from test reports easier for an end user. (Things like the Title and Found-In could be prefilled.) _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
