On Wed, Sep 10, 2014 at 6:35 PM, Ron W <[email protected]> wrote: > But given that an integration with an external issue tracker would, > itself, have to be customisable, I am hoping that the JSON API can at least > "transport" the custom fields. If it were also possible to query the > descriptions/meta-data of the custom fields, that would be even better. >
In principal, plain old transport is not the problem. The problem (as i recall it, though it's been a while and i've got the memory of a goldfish) was that i could not define a concrete structure for JSON/Ticket I/O because tickets are customizable. Suggestions are of course welcomed, and if there's a concrete case you or Eric have in mind, i can probably say whether it's currently workable or estimate what it would take to make it so. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
