CODE INTEGRATING PERFORCE WITH BTNET IS POSTED HERE

* HOW TO USE:

When submitting a Perforce changelist that you would
like to link to one or more BT.NET bugs, simply include
the bug id in the description with a preceding keyword.
For example:

- Fixed bug#4542 and added support for issue #70
- Created feature #34, according to spec
- Issue #0053 has been resolved
- Finally incorprated tweak#70

* WHAT IT DOES:

- Inspects the description of the new changelist and
extracts #id preceded by the words: issue, bug, feature
or tweak. Dupes are ignored, spaces are optional (0 or
more), case is insensitive

- Sets the referenced bugs status according to
configuration and logs the changelist id in the bug

- Updates bug history and comments according to
performed changes

- Attempts to match the perforce username and the
BT.NET username for accurate logging

* HOW TO INSTALL:

- Copy p4bt.js to the BT.NET directory

- Add a custom field via BT.NET's web interface with the
name "Perforce ID" (without the quotes) and set it to
type "int"

- Edit the Web.Config file

- Add the key PerforceSubmitStatus under
<btnetSettings> with the value of the final status to set
when a changelist is linked to a bug (5=closed in default
installation)

- Add the key ADOConnectionString under
<btnetSettings> with the value of an ADO-compatible
connection string to the BT.NET database

- Save and exit the Web.Config file

- Run the command "p4 triggers"

- In the editor that opens add the following text right
below Triggers: bugtrack //... "cscript
j:\path\to\bt.net\p4bt.js %changelist%"
The tab is intentional and should be there

- Save and exit the editor