#11650 closed defect (wontfix)
new ticket method queryDetailed
Reported by: | anonymous | Owned by: | osimons |
---|---|---|---|
Priority: | normal | Component: | XmlRpcPlugin |
Severity: | normal | Keywords: | |
Cc: | Olemis Lang | Trac Release: |
Description
Hi,
For our use case we would like to be able to get full info about a set of tickets from a query (representing holiday requests), without having to make a request for each ticket id.
Patch attached. Cheers Shez
Attachments (1)
Change History (5)
Changed 11 years ago by
Attachment: | tracrpc.patch added |
---|
comment:1 Changed 11 years ago by
Replying to anonymous:
Hi,
Hi ! :)
For our use case we would like to be able to get full info about a set of tickets from a query (representing holiday requests), without having to make a request for each ticket id.
Your use case would be solved by issuing two RPC calls .
ticket.query()
system.multicall()
wrapping signatures for multiple calls toticket.get()
Should you need any help then I could provide you with a working example . IMHO this ticket should be resolved as wontfix
.
@osimons : please feel free to do so on my behalf if you notice I take too long before doing so .
Patch attached.
Thanks , but in this cases there's no chance (afaict) for this to be committed .
comment:2 Changed 11 years ago by
Resolution: | → wontfix |
---|---|
Status: | new → closed |
comment:3 Changed 11 years ago by
Hi,
Will your solution result in 100 GET requests if there are a hundred tickets matched?
I was assuming it would, which is very sub-optimal for us, hence my patch.
Cheers! Shez
comment:4 Changed 11 years ago by
Apologies, with a little reading i see system.multicall should do the RPC calls internally on the server.
Cheers Shez
Patch to add new rpc ticket.queryDetailed endpoint