Kristis,
Basically there is not much difference. It is just that we implemented a
basic status changing back in 2007 with bugzilla 3.0 and Scmbug. This just
used the standard checkin methods with Scmbug, but if the status message
included 'RESOLVED-FIXED' keyword, we manually changed the status of the bug
in the database.
The reason we have not migrated to use the new official status changing is
because
1. the developers are used to doing this
2. if we check-in against multiple bugs, our 'hack' changes the status of
all bugs with the one keyword (In my view this is the correct behaviour - we
have a policy that check-in's should be complete for a single task
With the last version of Scmbug we were using (not sure the version, but the
first with status resolution) we changed our hack to call your change status
function (integration_change_bug_resolution) with the relevant
'RESOLVED','FIXED' values.
With the latest changes to support bugzilla 3.4.2, this did not appear to
work, so I spent some time to understand how the new bugzilla status
changing worked, and just called the bugzilla function within the
integration_add_comment function.
if ( $comment =~ m/RESOLVED-FIXED/i ) {
#$self->integration_change_bug_resolution($bugid,
$username, "RESOLVED", "FIXED", "");
$current_bug->set_status( "RESOLVED", { resolution =>
"FIXED" } );
}
Notice the commented line, which was our first attempt that did not work for
us.
Hope this makes sense.
I'd like to investigate the 'proper' status changing implementation, but we
have been quite busy recently! I'll probably wait until an official release
is available to support bugzilla 3.4.2 though.
Robert.
Robert G Ward
QA Manager
Site Intelligence Ltd.
e [email protected]
---------- Forwarded message ----------
From: Kristis Makris <[email protected]>
Date: Wed, Sep 16, 2009 at 10:11 AM
Subject: Re: [scmbug-users] Scmbug with Bugzilla 3.4.1 - status changing
To: Robert G Ward <[email protected]>
Cc: "'[email protected].'"@post4.inre.asu.edu
Hi Robert, I'm glad you got it to work for your needs.
> I've managed to work around this for the hack that I needed (we are not
> using full status changing, just allowing developers to mark a bug as
> resolved-fixed via a keyword in the checking message.
It's not clear to me; what is the difference between "full status
changing" and just marking something as resolved-fixed ?
------------------------------
_______________________________________________
scmbug-users mailing list
[email protected]
http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
End of scmbug-users Digest, Vol 49, Issue 5
*******************************************
_______________________________________________
scmbug-users mailing list
[email protected]
http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
