It should be possible to change the state of a bug, at least to close it. This would enable integration with systems that connects e.g. a cvs commit with a bug close.

Hmm. Looking at the code, this seems to be somewhat more complicated than I thought. Specifically, it seems the code to ensure valid status changes (from one status to another) is embedded in the cgi handling code? What would be a good approach to implement this in the webservice? Should the code be moved from the cgi part to core bugzilla, or duplicated in the webservice? Or another approach?

(In reply to comment #1) > What would be a good approach to implement this in the webservice? I think we need to complete the moving of process_bug code into Bugzilla::Bug, which we're going to do for 3.2.

Bugzilla 3.2 is now frozen. Only enhancements blocking 3.2 or specifically approved for 3.2 may be checked in to the 3.2 branch. If you would like to nominate your enhancement for Bugzilla 3.2, set the "blocking3.2" flag to "?", and either the target milestone will be changed back, or the blocking3.2 flag will be granted, if we will accept this enhancement for Bugzilla 3.2.

This bug doesn't even have a patch or an assignee, and we're frozen for 3.2, so I can't accept this on the branch in good conscience.