On Thu, Dec 14, 2017 at 7:00 AM, <fossil-users-requ...@lists.fossil-scm.org> wrote: > > Date: Wed, 13 Dec 2017 18:04:41 -0600 (CST) > From: Roy Keene <fos...@rkeene.org> > Subject: Re: [fossil-users] Fossil vs. GitHub > > One thing I often wish Fossil did was show other things (tickets, wiki > pages) that reference tickets rather than just checkins -- I often have a > mess of tickets that refer to other tickets and no place to generate a > list of them, or reverse them.
I'm not sure how the TH1 regexp command works, but it might be possible to at least find other tickets that reference a specific ticket using a combination of SQL in Fossil's ticket report subsystem and TH1+SQL in the new and edit ticket scripts in the ticket configuration. In the ticket configuration, add a new table to the ticket schema to that has 2 columns: "referree" and "referrer".. In the new and edit ticket TH1 scripts, enhance the submit handling to find artifact references using the regexp command with the regex "\[[0-9a-f]\]". For each match, add (or update) a row to the new table with referree = ID found and referrer = ID of current ticket. Of course, this assumes that the ticket TH1 scripts can access the ID of the current ticket and that the TH1 regexp command can be used to get a list of locations of regex matches. Maybe some Javascript can extract the ticket ID from the URL and supply that as a hidden field back to the TH1 scripts. If regexp doesn't work as needed, may be possible to use "string first" and "string range" to find and extract artifact IDs. As for wiki pages, maybe the "webpage_notify" hook can be used to find artifact references.
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
