bugtracker(2.1.4)中文版

BugTracker.NET Copyright 2002-2005 Corey Trager Distributed under the terms of the GNU General Public License This README.TXT contains information about how to setup BugTracker.NET, and some tips on how to use it. ----------------------------------------------------------------------- ----------------------------------------------------------------------- INSTALLATION ----------------------------------------------------------------------- ----------------------------------------------------------------------- 1. Create an IIS virtual directory and point it to this folder. 2. Create a database following one of the methods below. 3. Modify other entries in Web.config as desired. There are a lot of settings there to explore. 4. Logon as user "admin", password "admin". You might also want to add custom columns to the bug screen as desired. Just alter the bugs table like "alter table bugs add [My Custom Column] varchar(20) null". You might also want to alter the queries you see in the dropdown of the bugs page, create custom reports, set up your own statues, etc. CREATING A DATABASE **** IF YOU HAVE SQL SERVER: 1. Create a SQL Server database. 2. Open "setup.sql" in Query Analyzer 3. Update the database connection string in Web.config to point to your database. *** IF YOU HAVE MSDE THAT COMES WITH THE .NET SDK AND NO SQL SERVER TOOLS: 1. Modify the line in Web.config you find that looks something like this: <add key="ConnectionString" value="server=GATEWAY\NetSDK;database=app;uid=sa;pwd="/> to <add key="ConnectionString" value="server=[YOUR MACHINE]\NetSDK;database=MASTER;uid=sa;pwd="/> 2. open query.aspx in the brower 3. type "CREATE DATABASE [choose a database name ]" 4. Modify the line in Web.config again, changing "MASTER" to whatever database you just created. 5. Copy/paste the text in setup.sql into the text area and run it. ********************************************************************** **** **** W A R N I N G !!! **** W A R N I N G !!! **** W A R N I N G !!! **** ********************************************************************** If you are planning to use Bugtracker.NET on a public web server, you should delete the file query.aspx after you install, because it will execute whatever SQL is sent to it under certain conditions. If there is a users table, it will authenticate and require the user to be admin. If there is NOT a users table, it will allow anybody to do anything. The idea is that before installation, it's a tool to allow you to set up the database. Also, make sure the setting "AllowQueryEditingForNonAdmins" in Web.config is set to "0" ----------------------------------------------------------------------- ----------------------------------------------------------------------- Release notes are now in RELEASE_NOTES.TXT ----------------------------------------------------------------------- ----------------------------------------------------------------------- ----------------------------------------------------------------------- ----------------------------------------------------------------------- Tips: ----------------------------------------------------------------------- ----------------------------------------------------------------------- * Spend time reading through the comments in the Web.config file in order to understand your options. * If you have a problem, check the Sourceforge help forum at: http://sourceforge.net/forum/forum.php?forum_id=226938. You can also email me at ctrager@yahoo.com. * The queries used to populate the bugs page are customizable on a per user basis. Edit the user and pick the query you want from the dropdown. You can create your own queries to using the queries/add new query. You can create some custom queries using the search.aspx page, but if you know how to edit SQL by hand, then you can do much more. You can also use a pseudo variable in your SQL, "$ME", which is the userid of the current user. You can also use the "$ME" variable in your "reports" SQL. * You can configure the "categories", "statuses", "priorities" to be whatever you want. Using a combination of statuses and your own custom queries, you can customize the workflow. For example, you could create a "ready for test" status and a SQL query that only sees items "ready for test" to create a queue of work for the testers. * If there aren't enough bug fields, there are three ways for you to add them, listed below: #1 You can also have one "user defined attribute" dropdown that applies to all projects. See the "admin" page and also see these lines in Web.config: <!-- If category/project/status/priority are not enough bug attributes for you, here's one more that you can name yourself --> <add key="ShowUserDefinedBugAttribute" value="1"/> <add key="UserDefinedBugAttributeName" value="YourAttribute"/> #2 You can add custom columns to the bug table and they will show up in the edit_bug.aspx form. See the admin "custom fields" page. #3 You can add custom dropdowns to individual projects via the admin/ projects page. Use this for version numbers that ony apply to a specific project, or sub-modules of a project. * You can create hyperlinks to other bugs in your bug comments by using the format bugid#99 where 99 is the number of the bug you want to link to. So, in the text, "This bug is similar to bugid#123", the "bugid#123" would be a hyperlink to the edit_bugs.aspx page for bug 123. (Thanks to Brett Michael for this suggestion.) * If you are tracking things that aren't bugs, and the word "Bugs" bothers you, you can change the name of the application and the label "Bugs" to be whatever you want via Web.config. For example, you could call the app "Acme Mfg Customer Care" and use the word "Tickets" instead of bugs. See the AppTitle, SingularBugLabel, PluralBugLabel, BugLinkMarker in Web.config. * There's an HTTP gateway for adding bugs from other clients instead of browers. Send an HTTP request with a url like so: insert_bug.aspx?username=YOURUSERNAME&password=YOURPASSWORD&short_desc=YOUR+SHORT_DESC&comment=YOUR+COMMENT&projectid=YOUR_PJID The response will either be ERROR: followed by the specifics of the error or OK: followed by the bug id. * btnet_console.exe and btnet_service.exe are POP3 clients that fetch email and stuff them in the database as bugs. You configure the email accounts on the project screens - you can use a different email account per project. You can also respond to emails from within btnet and the responses are saved. Btnet_console.exe and btnet_service.exe do the same thing, but one is just a console app and the other is a service. Try running the cosole app first because it is verbose and will help you debug your configuration. Both of them get their settings from the "pop3Settings" section of you Web.config file or your "btnet_service.exe.config" copy (see below) of your Web.config file. Running btnet_console: Enter "btnet_console.exe Web.config" when you are in btnet's directory. Running btnet_service.exe: Use "installutil.exe" to install btnet_service. I know installutil.exe comes with the .NET SDK. I'm not sure how else to get it or whether it's ok for me to distribute it. Put a copy of your Web.config file, with correct settings, into the c:\ folder and rename it "btnet_service.exe.config". btnet_service.exe looks for its configuration at the hard-coded path of c:\btnet_service.exe.config. * BugTracker.NET sends email notifications. Getting that to work seems to be one of the trickier setup tasks. If you are having trouble: 1) Browse the Sourceforge help forum at: http://sourceforge.net/forum/forum.php?forum_id=226938 2) Make sure