Red Hat Bugzilla – Bug 427894
XMLRPC function getBugModified
Last modified: 2013-06-24 00:16:17 EDT
write xmlrpc function getBugModified that is to be contributed to the upstream. Please refer to the following url for details on Bugzilla::RPC 2.18 functions mapped to upstream Bugzilla::WebService and for 2.18 xmlrpc functions sorted by percentage of calls: https://engineering.redhat.com/trac/bugzilla-3.0-rh/wiki/XmlrpcCrossComparison#a2.18xmlrpcfunctionssortedbypercentageofcalls
This feature is included now in Milestone 2. Any bugs found with this feature should be file as a new report and set to block the 3.2 final release tracker.
Just a thought ,, As this function is one of the highly used functions in our xmlrpc interface,, Maybe in the WebSerivce Interface for 3.2 we can include it in Bug.get() ,, so we will pass delta_ts or creation_ts in the fields hash where we specify the fields we want in return. or maybe we can pass: last_modified in the fields array so we would get either delta_ts or creation_ts if the bug is newly created ? $rpc->call('Bug.get', { ids => [1,2], fields => ['last_modified']}); or we can have it as a separate function called Bug.get_last_modified $rpc->call('Bug.get_last_modified', { ids => [1,2]}); Thought? Noura
better to discuss this upstream I think. 1) this is derived information from two existing fields. I'd be careful about doing that. Don't they mean different things? If a bug is new then delta_ts will be empty. It was never modified. 2) yet another xmlrpc function? my vote is to use Bug.get
(In reply to comment #2) > Just a thought ,, As this function is one of the highly used functions in our > xmlrpc interface,, Maybe in the WebSerivce Interface for 3.2 we can include it > in Bug.get() ,, so we will pass delta_ts or creation_ts in the fields hash > where we specify the fields we want in return. or maybe we can pass: > last_modified in the fields array so we would get either delta_ts or creation_ts > if the bug is newly created ? > > $rpc->call('Bug.get', { ids => [1,2], fields => ['last_modified']}); > > or we can have it as a separate function called Bug.get_last_modified > $rpc->call('Bug.get_last_modified', { ids => [1,2]}); > > Thought? > > Noura I agree with Kevin. I do not see a need for another function here. I think making Bug.get return either delta_ts or creation_ts for a new bug will be sufficient. Also creating an alias called 'last_modified' would be useful so that people will not need to specify 'delta_ts' and 'creation_ts' manually to get the information they are looking for. Dave