2012-02-25 05:37 AEST by Arthur Barrett - Sometimes customers find the changeset number difficult.  It may present has them asking for a 
TortoiseCVS lookup screen for bug numbers, or it may present as them saying "we don't have bug 
numbers'.  What it seems to mean in practice is that they don't have a number, or it's not easily known.

eg:
a SAS customer may have just one 'bug'/'job' for each project (lung400) or one  'bug'/'job' for each 
project/sub-task, eg:

* lung400
* lung400-data
* lung400-prod (sas)
* lung400-val (sas)

In addition to a regular expression to find the changeset number, it would be great to have a regular 
expression to find the project/task, and then 'map' that to a changeset number.  

Ideally the mapping would be done by calling the defect tracking trigger to 'search' for a matching bug 
number.  But a simpler alternative (with no bug_trigger API changes) would be to look up a mapping file 
in CVSROOT (like the existing 'CVSROOT/users' file).