On Tue, Sep 30, 2014 at 2:17 PM, Stephan Beal <[email protected]> wrote:
> 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." > Using TH1, it is possible to encode various ticket handling steps. A few years ago, I shared the custom TH1 code I wrote for my team. We don't use it anymore. If I can find a copy, I'll post it, again. Or it should be somewhere in the archive of this mailing list (I haven't posted a ton of messages so it shouldn't be very hard to find.)
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
