Overview
Artifact ID: | 69b86fced760ea61b6101c875611bd669b593164 |
---|---|
Ticket: | 40a609e3c73ab63ce7eb92b2aec5cbe99810b283
Tickets MUST be listed in a DataTables table which is filled based on a TicketReport RN |
User & Date: | charlie 2018-03-08 17:37:11 |
Changes
- icomment:
# All tickets, the basis of the kanban info. http://localhost:8081/rptview?tablist=1&rn=1 The output of the above query is a good startingpoint to 'fetch the data'. Of course better options exist. But for an initial implementation, based on a stock fossil binary, it would be good to rely on this only. Options for future: use an actual query, or use the json compiled version of fossil as 'backend' API # On the matter of DataTable Datatables?: https://datatables.net/examples/basic_init/zero_configuration.html Probably the best option for generating a tabular view.
- login: "charlie"
- mimetype: "text/x-fossil-plain"
- priority changed to: "Immediate"
- resolution changed to: "Open"