I'm sure someone else asked this recently. http://wiki.eclipse.org/Mylyn_Integrator_Reference#Use_Cases has an appropriate set of actions
my take: 1. each ticket to have an unique URL and retrieve ticket attribute(s) by ID. Done! e.g. http://www.fossil-scm.org/index.html/tktview?name=5f194e2c8f475ce9d5e8bde058c1e97d683f3ce5 2. Search: query returning all of the matching task IDs, optionally with specified field, and matching field. (id, named fields, field(s) matched, matched field values), to enable quick pos-retrieval ranking, 3. Creating new tickets 4. Retrieving allowed operations on possible on a tickets fields (not-authorised,read-only, code-list, replace, append, delete?) 5. performing allowed operations on a tickets fields (append to description, change status to closed) 6. Adding and retrieving attachments (e.g. posting patches, screenshots) As for as what is actually transmitted received - the simpler to parse the better. (Fossil -style key-value pairs are fine, as is JSON) Stephen PS the new fossil site looks good! On Friday, March 4, 2011, Federico Ramallo <[email protected]> wrote: > Hi, > I was thinking it would be great to have a REST interface with the tickets. How difficult would be to implement? > I know there are some ways to parse and dump json from C, but I don't know the level of effort. > > The concept is to interact with the ticket system from JS and improve the UI.What do you think? > Regards,Federico Ramallo > >
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
