2009/11/17 Jacek Cała <jacek.c...@gmail.com>:
> I wonder if there is any simple way to add `blocker' feature to the fossil's
> ticketing system (I mean a list of tickets that prevent one to complete).

I'm not sure exactly what behavior a blocker feature would have, but see below.

> I tried adding 'CREATE TABLE blocker(...)' in
> the Admin->Tickets->Table page
> and then when creating a new ticket report it says:
>
> Syntax error: access to blockers.blockerid is prohibited

In the report_query_authorizer function in report.c
(http://fossil-scm.org/index.html/artifact?name=911a1c587a23d93838fb5f36001561a4834a535e),
I see a hard-coded list of allowed tables (ticket, blob, filename,
mlink, plink, event,  tag, tagxref).  Since any new table you create
is not in that hard-coded list, access to it will be blocked from the
reports.

> Is there any way to access a second table from the UI?

I don't think so.  Not without changing fossil's source code.

> Do you have any other ideas?

If what you are asking for is similar to the "derived ticket"
functionality in cvstrac (http://cvstrac.org), then you could just add
a column to the ticket table itself.  Maybe called 'blocker'.  It
would be a space separated list of ticket uuids.  On the new ticket
page and eidt ticket page, add a keyin box for this field.

Then on the view ticket page you could place hyperlinks to each of
these "blocker tickets".  Here is some th1 code to do this:

   pretend derived tickets:
   <th1>
   # Some ticket ids from my toy system.  If really doing derived tickets, then
   # this value should come from a column in the ticket table.
   set derived {9f9118480 3f85a6cf2b ed9a7c77df}

   # Loop through the ticket uuids
   for {set x 0} {$x < [llength $derived]} {set x [expr {$x + 1}]} {
     # Add braces so wiki formatter will make links.  Backslashes
     # hide those braces from interpretation by th1
     wiki \[[lindex $derived $x]\]
   }
   </th1>

It is likely possible to enforce that parent tickets not be closed
before all the child tickets are closed via an sqlite trigger.

Brian
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to