release_notes.txt

Bug管理系统

in web.config on how to avoid receiving a logon prompt.

* Receiving too many emails? Users can decide to receive only email 
notifications on new bugs, rather than receiving a change every time a
bug is changed. 

-----------------------------------------------------------------------
Migrating to 1.6.9 
-----------------------------------------------------------------------

Run this sql:

alter table users add us_only_new_bug_notifications int null default(0)
update users set us_only_new_bug_notifications = 0

-----------------------------------------------------------------------
Version 1.6.8 11/10/2003
-----------------------------------------------------------------------

SEE "MIGRATING TO 1.6.8" BELOW

I'm trying to make BugTracker.NET more secure, suitable for a public
web server.   I think at this point, it is secure from mischief from
unauthorized or non-admin users.   Admin users can pretty much do
whatever they want, so don't grant admin rights to somebody you don't
know and trust.

* Revised logon scheme.  Before the browser carried cookies that
indicated whether the user was authenticated and an admin user.   These
were simple cookies, easy to forge.   Now cookie is a guid that must
match up with an entry in the new "sessions" table.  

* Revised search.aspx so that it does NOT run the sql sent to it in
the HTTP request but instead reassembles it based on the contents of
the controls.

* Revised query.aspx so that IF there is a users table (i.e, post
installation), it will require that a user be authenticated and
admin.   The idea is to let anybody use it before installation, but
after installation only admins.

* Now calling HttpUtility.HtmlDecode for values from textareas before
storing them in the database.   I hope this doesn't break anything for 
you.    The intent is that when the subject or body contains html tags,
those tags should be stored in the database as written.   However, when
echoed back in the web pages, the text from the db should be Html 
encoded to prevent cross-site-scripting problems.  I think btnet is
safe from cross-site-scripting attacks from non-admin users.

* Fixed broken AllowQueryEditingForNonAdmins setting.   Web.config now
sets it to off by default.  Keep this turned off on a public web server.

* New "CommentSortOrder" in Web.config - set to either "asc" or "desc"
to control sort order of comments and history.

* New "Send Email" link from edit_bug.aspx to send_email.aspx.

-----------------------------------------------------------------------
Migrating 1.6.8  
-----------------------------------------------------------------------

Run this:

create table sessions
(
	se_id char(37) not null,
	se_date datetime not null default(getdate()),
	se_user int not null
)

-----------------------------------------------------------------------
Version 1.6.7  11/06/2003
-----------------------------------------------------------------------

!!PLEASE SET THE NEW "AbsoluteUrlPrefix" VALUE IN Web.config!!   

You need to configure it for the bug-to-bug hyper links to work.

* Email notifications now contain hyperlinks

* A bunch of little bug fixes.

* Minor cosmetic improvements


-----------------------------------------------------------------------
Version 1.6.6 11/02/2003
-----------------------------------------------------------------------

* You can save shortcuts and links to bugs.   When you click on link,
if you are not logged in, you will be presented with the logon page, 
default.aspx.    After logging in you will be redirected to the link.

* Quickly switch queries on bug page using new drop down

* Better, safer handling of user-entered text used to build SQL 
statements

-----------------------------------------------------------------------
Version 1.6.5 11/01/2003
-----------------------------------------------------------------------

Many thanks to Eugene Kalinin (http://sourceforge.net/users/ekalinin/)
for his input on this release.

* Now able to search on user defined attribute and last updated

* User defined attribute shows up in search results and in notification
email

* "Prev" and "next" links on edit_bug.aspx for navigating through list
of bugs without returning to the list.   

* Notification emails are now in Html format and include everything
you would see on the "print" page.

* Bug comments textarea is bigger for new bugs

* If you add a new bug, and then another, the project is initialized
to the previously used project.

* Logging now actually logs something: url, who the user is, and all the
sql.

* Added SmtpSendUsing setting in Web.config.  See below in the tips
section to see how the Web.config settings are used to configure email
messages.

* Fixed bug: btnet_service.exe, btnet_console.exe were not URL encoding
their request to insert_bug.aspx


-----------------------------------------------------------------------
Version 1.6.4 10/26/2003
-----------------------------------------------------------------------

* Automatically subscribe to bug notifications on a per-project basis.

* Added "settings" link.  Non-admin users can control their own user 
settings.

-----------------------------------------------------------------------
Migrating to 1.6.4
-----------------------------------------------------------------------

There is a new table.  To add the table to your database, logon, click 
on admin, click on run ad-hoc query, paste in the text below and submit.

create table project_user_xref
(
pu_id int identity not null,
pu_project int not null,
pu_user int not null,
pu_auto_subscribe int not null default(0)
)

create index pu_index_1 on project_user_xref (pu_project, pu_user)
create index pu_index_2 on project_user_xref (pu_user, pu_project)


-----------------------------------------------------------------------
Version 1.6.3 10/22/2003
-----------------------------------------------------------------------

* Search now searches comments too

* Added SmtpServerPickupDirectory setting in Web.config.   You probably
don't need it.

* Added InsertBugUrl setting in Web.Config - removed hard-coded 
127.0.0.1 URL from pop3 client


-----------------------------------------------------------------------
Version 1.6.2 10/03/2003
-----------------------------------------------------------------------

Various bug fixes, including:
* bug attachment links were not being displayed right in edit_bugs.aspx
* This README.TXT file said bc_type is a char(1) instead of a varchar(8)
* Dropdowns sometimes were not in any meaningful sort order

Also:
* Added line charts (in addition to pie and bar)

-----------------------------------------------------------------------
Version 1.6.1 09/21/2003
-----------------------------------------------------------------------

Added "reports.aspx".   It's a page that lists various summary reports
that you can view either as data or in pie or bar chart form.

Create your own reports by adding entries to the "reports" table.

* Renamed btnet_pop3.exe to btnet_console.exe.   There is also now
a version that runs as a service, btnet_service.exe.   See Tips
section below for how to setup up btnet_service.exe.

-----------------------------------------------------------------------
Migrating to 1.6.1
-----------------------------------------------------------------------

Run the following SQL

create table reports
(
	rp_id int identity not null,
	rp_desc varchar(80) not null,
	rp_sql varchar(1024) not null,
	rp_chart_type varchar(8) not null
)


insert into reports (rp_desc, rp_sql, rp_chart_type)
values('Bugs by Status',
'select st_name [status], count(1) [count] from bugs inner join statuses on bg_status = st_id group by st_name order by st_name',
'pie')

insert into reports (rp_desc, rp_sql, rp_chart_type)
values('Bugs by Priority',
'select pr_name [priority], count(1) [count] from bugs inner join priorities on bg_priority = pr_id group by pr_name order by pr_name',
'pie')

insert into reports (rp_desc, rp_sql, rp_chart_type)
values('Bugs by Category',
'select ct_name [category], count(1) [count] from bugs inner join categories on bg_category = ct_id group by ct_name order by ct_name',
'pie')

insert into reports (rp_desc, rp_sql, rp_chart_type)
values('Bugs by Month',
'select month(bg_reported_date) [month], count(1) [count] from bugs group by year(bg_reported_date), month(bg_reported_date) order by year(bg_reported_date), month(bg_reported_date)',
'bar')

insert into reports (rp_desc, rp_sql, rp_chart_type)
values('Bugs by Day of Year',
'select datepart(dy, bg_reported_date) [day of year], count(1) [count] from bugs group by datepart(dy, bg_reported_date), datepart(dy,bg_reported_date) order by 1',
'bar')

insert into reports (rp_desc, rp_sql, rp_chart_type)
values('Bugs by User',
'select bg_reported_user, count(1) [r] into #t from bugs group by bg_reported_user; select bg_assigned_to_user, count(1) [a] into #t2 from bugs group by bg_assigned_to_user; select us_username, r [reported], a [assigned] from users left outer join #t on bg_reported_user = us_id left outer join #t2 on bg_assigned_to_user = us_id order by 1', 
'table')


-----------------------------------------------------------------------
Version 1.6
-----------------------------------------------------------------------

* Added btnet_pop3.exe.  It's a POP3 client that fetches emails and
stuffs them in the database as bugs.  See "Tips" section below for more
info.

* BUG_HISTORY has been merged into BUG_COMMENTS.  See "Migrating to 1.6"
section below.

* Improved SMTP support - now able to specify a user/password for SMTP
servers that require authentication.   See in Web.config:
<add key="SmtpServerAuthenticateUser" value="YOUR SMTP USER NAME"/>
<add key="SmtpServerAuthenticatePassword" value="YOUR PASSWORD"/>

* Got rid of Authenticate.dll scheme.

* Fixed bug where notification emails had incorrect bug status, category,
project, etc. 

* Fixed bug where edit_user.aspx died with names like O'Hara, O'Malley.


-----------------------------------------------------------------------
Migrating to 1.6
-----------------------------------------------------------------------


1) There are new columns in the project table and bug_comments table.   To add the columns to
your database, logon, click on admin, click on run ad-hoc query, paste 
in the text below and submit.

alter table projects add pj_enable_pop3 int null 
alter table projects add pj_pop3_username varchar(50) null
alter table projects add pj_pop3_password varchar(20) null
alter table projects add pj_pop3_email_from varchar(50) null

alter table bug_comments add bc_email_from varchar(255) null
alter table bug_comments add bc_email_to varchar(255) null
alter table bug_comments add bc_type varchar(8) null

2) Bug comment and bug history tables have been merged into one
table and a bc_type field now distinguishes them.  The types are:
comment
update
received [email]
sent [email]

The following SQL updates the bug_comment -- copy data from history to comments and get rid of history table

update bug_comments set bc_type = 'comment'

insert into bug_comments 
(bc_bug, bc_user, bc_date, bc_comment, bc_type)
select bh_bug, bh_user, bh_date, bh_what, 'update'
from bug_history

drop table bug_history


2) Update the top of your Web.config file, so that it looks like this:

<configSections>
	<section
		name="btnetSettings"
		type="System.Configuration.NameValueFileSectionHandler,System, Version=1.0.3300.0,Culture=neutral, PublicKeyToken=b77a5c561934e089" />
	<section
		name="pop3Settings"
		type="System.Configuration.NameValueFileSectionHandler,System, Version=1.0.3300.0,Culture=neutral, PublicKeyToken=b77a5c561934e089" />
</configSections>


3) Add this after the line containing "</btnetSettings>".  Change the
actual settings to fit your situation.

	<pop3Settings>
		<!--
			Replace my server with YOUR server.
		-->
		<add key="Pop3Server" value="pop.sbcglobal.yahoo.com"/>

		<!--
			BugTracker.NET username, password that btnet_service.exe will use
			to talk to BugTracker.NET
		-->
		<add key="username" value="email"/>
		<add key="password" value="x"/>

		<!--
			Only retrieve messages if they contain a magic word in their subject.
			If the value is blank, then btnet_pop3.exe will retrieve all messages.
			Probably for your production, the value should be blank.
		-->
		<add key="SubjectMustContain" value="test"/>
		<!--
			For my own testing, it was useful to have this option.
			For production the value should be 1.
		-->
		<add key="DeleteMessagesOnServer" value="1"/>

		<!--
			How frequently should btnet_pop3.exe check the server for emails?
		-->
		<add key="FetchIntervalInMinutes" value="15"/>

	</pop3Settings>
 
-----------------------------------------------------------------------
Version 1.5.1
-----------------------------------------------------------------------

* Added view_web_config.aspx to view Web.config file for admins
* Added ability to delete bugs
* Web.config gives more control over what non-admins are allowed
to do.  
* Web.config controls whether raw SQL displays on the query and search
pages
* Web.config controls whether bug change history entries are show with
bug comment entries or seperately

-----------------------------------------------------------------------
Version 1.5
-----------------------------------------------------------------------

Migrating from 1.4 to 1.5


There are new columns in the project table.   To add the columns to
your database, logon, click on admin, click on run ad-hoc query, paste 
in the text below and submit.

alter table projects add pj_default_user int null
alter table projects add pj_auto_assign_default_user int null
alter table projects add pj_auto_subscribe_default_user int null


-----------------------------------------------------------------------
Version 1.4
-----------------------------------------------------------------------

* New print bug feature
* Revised database access layer to - was architected all wrong.  You
shouldn't even use versions prior to 1.4 anymore.  Sorry.