Thank you for the suggestion, exporting reports from the CLI has it's uses, but what I was trying to do is to provide links to an external system.
I noticed that using an "_" at the start of a column name makes it possible to use wiki strings, which would successfully create links, but the problem is that this will break the columnar format of the report, as these fields will be on rows by themselves. Useful, but not what I needed right now. Regards On Wed, Feb 18, 2015 at 11:51 PM, Ron W <ronw.m...@gmail.com> wrote: > > > On Wed, Feb 18, 2015 at 4:11 PM, Fadi Mansour < > fadi.redeemer.mans...@gmail.com> wrote: > >> I managed to customize the "View Ticket" page to create links from the >> text found in this field, but for reports, there's only the query, and I'm >> not sure if I have access to the logic that is rendering the result of this >> query. >> > > Once upon a time, I considered the possibility of an enhancement to Ticket > Reports to specify TH1/TCL "filter" code that would be called once for each > ticket The filter could modify the named fields "in place" and possibly > return status to indicate whether the ticket should be included or skipped. > > While I still think it would be useful, our reports are currently "New > Tickets", "My Tickets", "Export Open" and "Export Closed". The 2 export > reports are used via the CLI to produce CSV files for managers to look at > in Excel (which seems to be their preferred UI for everything). > > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > >
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
