Account confirmers, Anti-spam team, Confirmed users, Bureaucrats and Sysops emeriti
4,925
edits
Bugzilla:BzAPI:Methods: Difference between revisions
Jump to navigation
Jump to search
no edit summary
(Created page with '==Bugs == === Search for bugs (/bug GET) === '''Input''' A) Search parameters, exactly as powerful as query.cgi but using the field names from th…') |
No edit summary |
||
| Line 1: | Line 1: | ||
==Bugs == | ==Notes== | ||
* All times are supplied as UTC, in the ISO 8601 extended format (e.g. "2009-06-21T12:34:56Z"). This should define the time unambiguously, and should be widely and easily parseable, at the expense of probably not being directly displayable without a little manipulation. | |||
* Votes are not supported. | |||
* Examples are in JSON format because I had to pick one; see above regarding other formats. | |||
==Bugs== | |||
=== Search for bugs (/bug GET) === | === Search for bugs (/bug GET) === | ||
| Line 77: | Line 83: | ||
'''Notes''' | '''Notes''' | ||
* If you pass a last_change_time, this call will check for editing conflicts. If you do not, it will unconditionally update the bug to the state you send. If there is a conflict, conflict resolution must be implemented by the client re-GETting the resource, resolving the conflict and re-PUTting the resolved version. | |||
* You can only add one comment per call. Add a [[Bugzilla:REST_API:Objects#Comment|Comment]] object without an id to the comments array. | * You can only add one comment per call. Add a [[Bugzilla:REST_API:Objects#Comment|Comment]] object without an id to the comments array. | ||
* This call does not support the updating of attachment metadata. Make a separate call to update attachments. | * This call does not support the updating of attachment metadata. Make a separate call to update attachments. | ||
| Line 239: | Line 246: | ||
'''Notes''' | '''Notes''' | ||
* If you pass a last_change_time, this call will check for editing conflicts. If you do not, it will unconditionally update the bug to the state you send. If there is a conflict, conflict resolution must be implemented by the client re-GETting the resource, resolving the conflict and re-PUTting the resolved version. | |||
* You can't set the same (multi-settable) flag twice on a single attachment submission | * You can't set the same (multi-settable) flag twice on a single attachment submission | ||
* To make this call check for conflicts, submit the last_change_time you received when getting the attachment data. To make unconditional updates (be careful!) simply do not supply a last_change_time. | * To make this call check for conflicts, submit the last_change_time you received when getting the attachment data. To make unconditional updates (be careful!) simply do not supply a last_change_time. | ||