Hi Drew, You can disable valid_product_name so that product name checking is not applied at all:
http://files.mkgnu.net/files/scmbug/SCMBUG_RELEASE_0-25-3/manual/html-single/manual.html#VERIFICATION-CHECKS-VALID-PRODUCT-NAME That's probably what you need here. Even if product_name_definition is set to manual, if you disable valid_product_name you should be able to at least commit. On Fri, 2008-05-02 at 10:17 -0400, Drew Marold wrote: > (server part, client part, web part, etc). All code is under a single > repository, logically broken up in to .NET and java trees. None of the > path names are going to easily map to bugzilla products. I looks like my > only choices are set it to manual, and get one product name, or auto, > where regexes won't help me. I would love to see a mapping option like > there is for usernames. Any suggestions on how to work with this ? > Changing all our bugzilla definitions really isn't an option. That would be a very valuable feature: http://bugzilla.mkgnu.net/show_bug.cgi?id=1169 Some ideas where proposed related to this -- to build that mapping option: http://bugzilla.mkgnu.net/show_bug.cgi?id=775#c12 > Also if you are committing an integration against an existin bug, why > not query bugzilla for the product name and use that ? Is that just too > heavy a process ? Because if a user supplied a wrong bug id (e.g. out of a different product name), we will let through the commit against the wrong bug. You won't like that; the integration comments will be misplaced. That's the whole reason we ask for the Prouct name beforehand: to make this verification, which can be disabled with valid_product_name
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
