>    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 ?

RR



2010/10/5 Wolfgang <rat...@stumvolls.de>:
> Christian Busch <busch.christ...@...> writes:
>
>  :
>> Will fossil have a kind of api or cmd line support for the ticket system
>> in some future?
>>
>> The inverse problem will appear as well. Having all this tickets in
>> fossil, I'd like to extract the information in some report format.
>  :
>
> Hi
>
> On branch wolfgangTicket with checkin 9d3b9d653a you'll find a first version,
> supporting show/add/set commands for tickets. The built in help text is shown
> below.
>
> I think it should fulfill most requirements, even linking an external gui to
> the fossil application
>
> E:\test>fossil help ticket
> Usage: fossil.exe ticket SUBCOMMAND ...
>
> Run various subcommands to control tickets
>
>    fossil.exe ticket show REPORTNR ?TICKETFILTER? ?-l|--limit LIMITCHAR?
>
>        Run the the ticket report, identified by the report number
>        used in the gui. The data is written as flat file on stdout,
>        using "," as separator. The seperator "," can be changed using
>        the -l or --limit option.
>        If TICKETFILTER is given on the commandline, the query is
>        limited with a new WHERE-condition.
>          example:  Report lists a column # with the uuid
>                    TICKETFILTER= [#]='uuuuuuuuu'
>
>    fossil.exe ticket set FIELD VALUE ?FIELD VALUE ... ? TICKETUUID
>
>        change ticket identified by TICKETUUID and set the value of
>        field FIELD to VALUE. Valid field descriptions are:
>           status, type, severity, priority, resolution,
>           foundin, private_contact, resolution, title or comment
>        Field names given above are the ones, defined in a standard
>        fossil environment. If you have added, deleted columns, you
>        change the all your configured columns.
>        You can use more than one field/value pair on the commandline.
>
>    fossil.exe ticket add FIELD VALUE ?FIELD VALUE ... ?
>
>        like set, but create a new ticket with the given values.
>
>
>
>
>
> _______________________________________________
> 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

Reply via email to