2013/10/2 Stephan Beal <sgb...@googlemail.com>
> On Wed, Oct 2, 2013 at 3:51 PM, Jacek Cała <jacek.c...@gmail.com> wrote:
>
>> ...For those interested I report changes to the ticket table (below) and
>> view and edit pages (attached source). A remaining issue is that as
>> there're no hard db constraints on blockers there seems to be no way to
>> verify that the blocker to be added is actually a valid ticket uuid.
>> Basically, user can add any text as a blocker.
>>
>
> Any "real" blocking support has to be integrated with the system as a
> whole, from the human processes to the software (but primarily the human
> processes). What does a "block" actually "block"?
>
I'd say it is as simple as it sounds: it just blocks another ticket from
closing, meaning that when you look at the view page and see some blockers
you may want first to check whether they've already been closed.
I didn't expect it to be a "rocket" feature but exactly a client-side
customization others {may/may not} find useful.
Jacek
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
