On Tue, Sep 30, 2014 at 6:43 PM, Paolo Bolzoni < [email protected]> wrote:
> I am using fossil for bug tracking in a project where (not my > decision) we use git for revision control. I was wondering if > there is a way to explicitly mark a ticket as children of > another. So it is clear that the root one must worked on before > the child one. > > It is possible do something like that? > There's nothing at the infrastructure-level which directly supports that, but you could add a custom field which holds a list of other ticket IDs. Fossil would apply no special logic to it, though, e.g. "can't do a release so long as this blocker ticket is opened." -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
