process_bug.cgi as backend and dontchange
Bradley Baetz
bbaetz at student.usyd.edu.au
Sat Oct 26 02:52:18 UTC 2002
On Fri, 25 Oct 2002, Christian Reis wrote:
> The problem isn't with the interface changing, but rather with it making
> what I need to do impossible. I'm using Gerv's suggestion to use id_XXX
> (simulating a mass change) and it works fine for now; hopefully, the
> same facility will be offered when process_bug changes by some HTTP (or
> XML-RPC, if that's where we will end up) interface script that can be
> used by software without access or permission to access the bugzilla
> database directly.
Well, eventually you'll do;
my $bug = new Bugzilla::Bug($bug_id);
$bug->add_comment("foo");
$bug->resolve("FIXED");
$bug->commit();
or something along those lines.
Note the emphasis on 'eventually' :)
Bradley
More information about the developers
mailing list