Hi Robert, I'm trying to understand if what you are describing justifies a new policy.
I understand that status resolution in Scmbug is not working yet for Bugzilla 3.2 and 3.4. That's a separate issue. > 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 Would it be useful for you to have a policy related to status resolution that requires a status resolution change to describe, at a minimum, a resolution of all the bugs against which a changeset is commited ? e.g. in the following example, a changeset is committed against bug 547 and bug 600, and, since a status change is also described, the status change must include bugs 547 and 600, although it can include other bugs (like bug 744) bug 547,600: Implemented automatic status resolution as a new policy. This seems to work but will need improvements in the testsuite. status 547,600,744: RESOLVED FIXED Thanks for your feedback. Kristis
signature.asc
Description: This is a digitally signed message part
_______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
