Hi,
It was not easy for me to discover that REPORTNR refers to one of
the "report formats" listed in the "Tickets main menu page". I would
explain it more detailed in the help, maybe using REPORT_FORMAT_NUMBER
instead of REPORTNR
At the same time, as the result of this command is a table, there
should be two delimiters instead of one. One for the rows and another
one for the columns. Also, what to do when the delimiter character is
contained in one of the fields? Maybe you should check the CSV format
for ideas.
Another problem is that this solution is not adequate for an
automatic GUI that should be useful for any fossil database. The GUI
cannot create automatically a new report format without user
permission and new fossil databases only contain by default the report
"All Tickets".
I see three solutions here:
1- All new fossil databases contain, by default, a report with name
"All open tickets" (then, the new command should permit to select it
by name)
2- The SQL for the report is embedded in the fossil command
3- Add a special subcommand:
fossil.exe ticket list -status Open fieldList ?-l|--limit LIMITCHAR?
This command only works for tickets that have a "status" field.
If a tickets table does not have the "status" field, nothing is
returned.
RR
2010/10/5 wolfgang <rat...@stumvolls.de>:
> Ramon Ribó <ram...@...> writes:
>
> :
>> > fossil.exe ticket show REPORTNR ?TICKETFILTER? ?-l|--limit LIMITCHAR?
>>
>> What is REPORTNR?
>>
>> > I think it should fulfill most requirements, even linking an external gui
>> > to
>> > the fossil application
>>
>> How do you list all tickets that are not closed or fixed, with its
>> basic data of:
>> TICKETUUID,title,status ?
> :
>
> The reportnumber is the internal id of reports, defined on the tickets
> page(reportlist). You'll find a list of valid reports, each uses an internal
> number, which can be seen as argument "rn" in the URL, if you call this
> report.
>
> Maybe i'll add the ability, to call the list with the report name.
>
> Because the ticket table can be configured, we cannot use a 'standard report',
> because we do not know, which names we have to use, to generate a standard
> report, as the one, you mentioned.
>
> If you want such an report, you have to define it inside fossil. Take a look
> at
> the reports, defined at fossil-scm.org. You can add the WHERE-condition to the
> report definition, so you don't have to filter it when calling the "fossil
> ticket show" command. For the original fossil-scm repository, the report 2 /
> all
> open tickets should match your requirements.
>
> best regards
> Wolfgang
>
> _______________________________________________
> 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
