Softpedia >Windows >Programming >Components & Libraries >BugTracker.NET >  Changelog

BugTracker.NET Changelog

What's new in BugTracker.NET 3.6.8

Dec 27, 2019
  • Fixed "folder not found" errors, especially when running install_btnet.cmd

New in BugTracker.NET 3.6.6 (Jan 2, 2019)

  • * Possibly fixed undefined "foo" error in add_attachment.aspx.

New in BugTracker.NET 3.6.5 (Nov 25, 2017)

  • Fixed bug where custom fields of type "user" would loose their value
  • If the update didn't work because of a validation error.
  • Fixed bug where custom field of type "datetime" didn't display with
  • Correct format in view only.
  • Fixed bug where app crashed if somebody update the bug's project
  • When view only fields were being displayed.
  • Custom fields of type datetime now display correctly in view only
  • Mode.
  • Deleted stuff that doesn't work anymore: Firefox addon, tropo (phone)
  • Thing.

New in BugTracker.NET 3.6.4 (Jul 3, 2014)

  • Fixed security vulnerability that allows unauthenticated users to post new bugs or add comments to existing bugs. You can either upgrade to this release or just delete the file "tropo_recording.aspx".

New in BugTracker.NET 3.6.3 (Apr 4, 2014)

  • Fixed bug with extracting plain text bodies from emails that aren't
  • multipart. Thanks Mike T for sending me the email sample.
  • Fixed bug where customer user dropdowns weren't getting reloaded.
  • Thanks to Raphael for the fix.
  • Fixed bug where custom date field was recorded as being changed in
  • the history, even though it wasn't changed. Thanks to Brettski for the
  • fix.

New in BugTracker.NET 3.6.2 (Mar 11, 2013)

  • Bypassing logic to handle SSL certificates when SSL is not being used for email. This fixes a Medium Trust issue at some hosting providers.
  • No longer setting max-width in css for popup previews that show up when you hover in a bug list (which didn't work in IE, Firefox anyway...).
  • Fixed bug that caused edit_bug.aspx to sometimes complain of null when saving.
  • Fixed return() bug in print_bug.aspx.

New in BugTracker.NET 3.6.1 (Jan 28, 2013)

  • Fixed bug where the email body wasn't always being found in the incoming emails
  • Fixed bug with view-only custom fields disappearing in view
  • Fixed bug "Validation causes wrong change history for custom fields"
  • Re-arranged the code in edit_bug.aspx A LOT. It's a lot easier to read and work with now.

New in BugTracker.NET 3.6.0 (Jan 23, 2013)

  • Fixed null bug in util.cs introduced in 3.5.9
  • Added some mobile pages. Before you enable them via Web.config, note
  • that the mobile pages *DO NOT* obey org permissions at all, nor
  • do they obey project permissions properly. If you rely on the
  • permission scheme, do not enable the mobile pages.
  • They are also very limited in what they show and what they allow you
  • to edit - description, project, status, assigned to, and comment.
  • Having said all that, if you want to try them out, add the following
  • to Web.config and then point your browser to mlogin.aspx.

New in BugTracker.NET 3.5.9 (Nov 14, 2012)

  • I actually learned a whole new type of vulnerability from them, "HTTP
  • Response Splitting".
  • I'm not sure that the vulnerabilities they reported to me are that scary mainly because many of them are in pages that only admins can access. Given that in BugTracker.NET, an admin can run free-form SQL, deleting data, etc, there's no need for an admin go through the back door when he can go through the front door.

New in BugTracker.NET 3.5.8 (Nov 14, 2012)

  • Updated "editarea" which fixes bug 3535159 "Missing www/edit_area/images/close.gif"
  • Fixed bug 3535164 "Custom validations error messages are not cleared".
  • Fixed bug 3505079 "SVN integration - empty svn_diff page for binary files" because of a typo.
  • Fixed typo in bug.cs related to org permissions for tags.
  • Fixed date formatting of Excel export.
  • Fixed bug where list of custom fields was displaying wrong length for nvarchar and nchar.

New in BugTracker.NET 3.5.7 (Jun 18, 2012)

  • Fixed XSS vulnerabiliy related to custom text fields. If you use custom text fields and if you expose your BugTracker.NET to users that you don't trust, you should upgrade to this release.
  • Added new setting in Web.config "SqlCommand.CommandTimeout", for inserting large attachements in the db.
  • Added some logging to help diagnose Web.config misconfigurations.

New in BugTracker.NET 3.5.6 (Feb 24, 2012)

  • For now, removed the dependency on .NET 4.0 in global.asax. Although the note at the top says BugTracker.NET requires .NET 4.0, I'm not yet using any 4.0 language features. I removed the dependency because my own GoDaddy shared hosting account doesn't support 4.0.
  • Fixed security hole whereby BugTracker.NET user belonging to an organization marked "external" could view posts marked "Visible to internal users only".
  • "export to excel" now works with non-ascii characters.
  • Fixed HTML encoding/decoding bugs with custom fields and when you edit
  • SQL statements.
  • Sending email no longer cares if the SMTP's SSL certificate is not
  • from a trusted authoritiy or if its domain name doesn't match the
  • actual domain name.
  • Fixed bug in btnet_screen_capture.exe where it wasn't saving its
  • the password.

New in BugTracker.NET 3.5.5 (Nov 21, 2011)

  • Fixed bug with pop3 logic where it wasn't handling an incoming email
  • referencing a bug that had been deleted.
  • Plus very minor fixes:
  • Added date/time to screen capture utility's screenshots. Also, fixed
  • a bug where it wasn't delaying enough when capturing full screen.
  • Added favicon to a couple more pages (but not everywhere)
  • Hiding "AUTH_PASSWORD" when errors are logged.

New in BugTracker.NET 3.5.4 (Nov 21, 2011)

  • Fixed bug where the pop3 thread wasn't truncating email subjects that
  • were too long for the db.
  • For the Subversion integration, you can now link one commit to
  • multiple bugs by entering the list as comma delimited:
  • ,22 my checkin comment
  • You need to change your Web.config Regex patterns for this to work:
  • Both a certain JW and Richard Housley sent me their implementations
  • of this feature which gave me the push to add it, althought I didn't
  • use their implementations. Thanks to them both.
  • Fixed bug using the Subversion-related web pages where files in the
  • repository had been renamed. The fix loosens the security a bit I
  • implemented in version 3.2.9, so this fix is off by default. If you
  • want the fix, set "SvnTrustPathsInUrls" to "1" in Web.config.

New in BugTracker.NET 3.5.3 (Nov 21, 2011)

  • IMPORTANT: Now using .NET 4.0 (and Visual C# 2010 Express) to
  • compile the exes. If you don't want to / can't run 4.0, use the
  • binaries from 3.5.2. For the web pages, the changes so far are just in
  • Web.config but eventually I may start using 4.0 language features.
  • IMPORTANT: Added setting "ShowPotentiallyDangerousHtml" to
  • Web.config. HTML attachments to bugs or emails could contain
  • malicious javascript. BugTracker.NET before version 3.5.3 made it too
  • easy to view these attachments. Now by default, BugTracker.NET does
  • not show html attachments when you click on "show images inline"
  • and does not display a "view" link. Thanks to Mateusz Dobrowolny for
  • patiently convincing me of the necessity of this change. Even if you
  • don't want to use the entire 3.5.3 release, you should apply the
  • changes that are in App_Code/print_bug.cs.
  • Added "watchdog" thread to btnet_service.exe, btnet_console.exe,
  • which, if it detects that the mail fetching thread is stalled, kills it
  • and spawns another. This is a workaround because some of the logic
  • in the POP3Client.cs file issues calls that block until there are bytes
  • to be read.
  • Automatic replies to email addresses like this were causing problems
  • because of the comma:
  • Smith, John
  • Added setting "EmailAddressSeparatorCharacter" to Web.config. Use it
  • if you want to change the separator from the default comma to a
  • semicolon.

New in BugTracker.NET 3.5.2 (Aug 2, 2011)

  • Announcement: BugTracker.NET now supports voice integration.
  • Fixed bug where you couldn't see more than 30 or so tasks because the
  • frame wasn't showing scrollbars.
  • Fixed bug where somebody editing a rich text comment who is not using
  • the rich text editor would wrongly see the HTML markup codes.
  • For .NET 4, you will need this in your Web.config system.web section:
  • httpRuntime requestValidationMode="2.0" />
  • More choices in the "from" dropdown in send_email.aspx. You can send
  • with or without your display name.

New in BugTracker.NET 3.5.1 (Jun 22, 2011)

  • "install.aspx" has a SQL injection vulnerability fixed

New in BugTracker.NET 3.5.0 (May 7, 2011)

  • Resizable textarea customfields were either too narrow or too wide in IE (ok in Firefox and Chrome). Changed btnet_base.css. Thanks to Ed Lance for this fix.
  • Added work around, null check of "stuff_to_delete" in email.cs. Not sure why it's ever null, but the workaround seems ok. Thanks to both Marko Hoven and Clifton Royston for this fix.
  • Some problems related to HttpRuntime.Cache.Add. Thanks to Piotr Owsiak for this fix.
  • Fixed bug when "> is entered into custom text field.
  • Fixed bug where users created from LDAP weren't having their email signatures populated.
  • Updated Firefox Add-on for Firefox 4.

New in BugTracker.NET 3.4.9 (May 7, 2011)

  • First of all, if you have installed BugTracker.NET recently, can you take a look at your Web.config and make sure the email address in "ErrorEmailTo" isn't [email protected]? I accidently left that in the Web.config I ship and now I'm getting many error emails per day. Thanks!
  • Fixed bug with pop3 thread, "pop3:exception in fetch_messages: Specified cast is not valid". This is in the new worker thread approach, not btnet_service.exe. Thanks to Werner van Deventer for this fix.
  • Fixed bug with custom dropdown fields of type "users" when displayed with a view only permission. The integer user_id was being displayed instead of the name.
  • Fixed bug where edit_styles.aspx was looking for btnet_custom.css in the root folder instead of the "custom" folder.
  • Fixed incompatibility with ASP.NET Medium Trust when sending emails.
  • See the "SmtpForceSsl" in Web.config.
  • Fixed bug when adding a subscriber to notifications with view_subscribers.aspx. The user you added was supposed to automatically get a notification right then, but the bug was preventing that from happening.
  • print_bug.cs now handles exceptions when trying to read in css files.
  • I'm having a problem with this intermittently at GoDaddy - I don't know why...
  • edit_custom_html.aspx now allows you to edit btnet_custom.css.

New in BugTracker.NET 3.4.8 (Dec 25, 2010)

  • Fixed bug introduced in 3.4.7, where send_email.aspx was forcing you
  • to supply a CC address.
  • Fixed bug where the "forced project" feature wasn't working with bugs
  • entered via insert_bug.aspx (email and screen capture).
  • Made cosmetic improvements in send_email.aspx, and I made it easier
  • to use display names in "to" and CC addresses.
  • Made the yellow highlighter a little faster in the screen capture
  • utility.

New in BugTracker.NET 3.4.7 (Dec 20, 2010)

  • This release contains an experimental feature, the ability to fetch email from a pop3 server using a thread spawned from the ASP.NET app instead of using a standalone service. You configure the settings using Web.config, using the keys that start with "Pop3", instead of using btnet_service.exe.config.
  • If you try this feature, please send me feedback. Even if you feedback
  • is just, "it works".
  • I tried this at my demo site on a shared host at GoDaddy.com, but it doesn't work: It conflicts with Microsoft's default "Medium Trust" setting and even GoDaddy's relaxed version of it.
  • Read more about this feature in Web.config, witht he settings whose names start with "Pop3".
  • As part of creating this feature I heavily revised insert_bug.aspx, so that the two ways of handling incoming emails could share code. Hopefully I didn't break anything, but I wanted folks to know that there is a bit more risk with this release.
  • Other changes:
  • If you have created a "btnet_css_for_email.css" file, the logic now looks for the file in the "custom" folder. This is to work around a Medium Trust issue at GoDaddy.
  • "LdapUserDistinguishedName" now supports multiple values, seperated
  • by "|" chars.
  • Better handling of email addresses in general, I hope, but specifically, email addresses with umlauts.
  • New Web.config setting "AutoReplyUseHtmlEmailFormat". The default
  • value should work fine, no need to chaneg it.
  • The screen capture utility's yellow marker's color/opacity is better, the way it should be. This is a small detail that probably only matters to me, as a programmer, but it was really bothering me; I spent about 4 hours on it.

New in BugTracker.NET 3.4.6 (Dec 20, 2010)

  • Fixed SQL error when using search.aspx with custom project fields.
  • Created some pages to make it easier to admin BugTracker.NET without
  • having FTP or direct access to the server. You get to these new page
  • from the admin page.
  • "Edit Custom HTML" to make it easy to customize the html header, footer, logo, etc.
  • "Edit Web.config" for editing Web.config. It will check your XML syntax before letting you save, but you can still shoot yourself in the foot.
  • "Backup Database" to make it easier to create and download backups of the db. This won't work at GoDaddy, though, because of their permissions.
  • "Manage Logs" to view/delete logs.
  • Upgraded CKEditor from 3.0.1 to 3.4.2.
  • Revised how the firefox extension saves configuration info, especially the password.

New in BugTracker.NET 3.4.5 (Dec 2, 2010)

  • I added the code for a new Firefox add-on that does screen captures. If you are on Windows, use the desktop app, but if you have users who are reporting bugs in web apps and they are not on Windows, the Firefox add-on might be useful. You can download the add-on here: http://ifdefined.com/bugtrackernet.html#firefox
  • Fixed a bug whereby in some configurations, email notifications were not being sent. If your send_email function works, but your email notifications don't work, this might fix your problem. It did fix the problem for at least one person.
  • Prevented errors and error emails from being trigged by "Microsoft
  • Office Existence Discovery" when using view_attachment.aspx.
  • Fixed a bug in the mass edit feature, changing orgs.

New in BugTracker.NET 3.4.4 (Dec 2, 2010)

  • There's only one change, a fix to a SQL injection vulnerability in search.aspx. Thanks to Mark van Tilburg for letting me know. This vulnerability is several years old.
  • If you don't want to upgrade, you can instead modify your copy of search.aspx, adding the logic to replace single quotes with double quotes in the same places where I did: http://btnet.svn.sourceforge.net/viewvc/btnet/www/search.aspx?r1=559&r2=565

New in BugTracker.NET 3.4.3 (Aug 19, 2010)

  • You will have to change your Web.config SMTP settings for this release.
  • I'm switched from using the old deprecated System.Web.Mail to the
  • newer System.Net.Mail. Your SMTP settings now come from the standard
  • system.net elements in Web.config. The Web.config that
  • I've included should be enough to show you how to reconfigure your
  • email settings. There are settings, commented out, that work for me
  • for GMail's SMTP service and GoDaddy's SMTP service if you are hosting
  • there.
  • Other changes:
  • Fixed but where external users weren't seeing the full list of users that they were supposed to see. Thanks to Jason Taylor for the fix.
  • You can now change the "reported by" user with the mass edit feature in the search.aspx page.
  • The screen capture utility now uses the descriptions you type in for the screenshot descriptions, not just the original bug description. Thanks to Javier Feria for this improvement.
  • The screen capture utility now works with Windows authentication, although I haven't personally tested it. I can say that the change doesn't break anything. Thanks to Lars Wuckel for thsi enhancement.

New in BugTracker.NET 3.4.2 (Aug 19, 2010)

  • Values in project custom dropdowns where being lost if bug was
  • updated by somebody with "Reporter" permission. Thanks to Ian Girouard
  • and Jean François Coté for the fix.
  • Tags search was wrongly being hidden if category field was hidden.
  • Thanks to Mike Abramovitch for the fix.
  • Fixed bug 3007867 "User friendly time in news page is sometimes wrong"
  • Thanks to Martin Richter for the fix.
  • "Save search as query" button wasn't working in Chrome
  • The "Add new" now is hidden now when you are actually in the process
  • of adding a bug. So that you don't hit it and lose your work. How many
  • times have I myself hit that link thinking I was saving the bug I had
  • just entered? Thanks to Dan Rye for this obvious-but-I-guess-not-so-obvious
  • fix.
  • Printing of bug and notification emails now show Tasks.
  • Adding/editing of tasks now triggers email notification and is
  • recorded in bug's history.
  • Lucene highlighting now controlled by css class "highlighted".

New in BugTracker.NET 3.4.1 (Aug 19, 2010)

  • For the tasks/time tracking feature, added a way of viewing all
  • the tasks at once, not just the tasks for one bug. Also added a way of
  • exporting all the tasks into Excel. These features are weak, but
  • they are better than nothing.
  • Fixed merge bugs feature. It wasn't merging tasks, flags, and
  • svn/hg/git data.
  • Added checkbox to send_email.aspx page that controls whether the
  • "comments visible to internal users only" are included in the email
  • body.
  • Corrected Web.config comments for "NotificationSubjectFormat". Added
  • ASSIGNED_TO$ as one of the variables.

New in BugTracker.NET 3.4.0 (Aug 19, 2010)

  • In screen capture app, "Go to website" now goes to the bug you just
  • created.
  • In screen capture app, fixed where the crosshairs weren't always
  • topmost.
  • In subversion hook script, fixed handling of URLs with spaces.
  • Fixed handling of tags with apostrophes (single quotes).
  • Fixed bug 2957930 where unusual characters didn't work right in
  • custom dropdowns. Thanks to cjundt for the fix.

New in BugTracker.NET 3.3.9 (Aug 19, 2010)

  • I messed up btnet_screen_capture.exe in 3.3.8. The only change
  • here is the screen capture program. If you downloaded 3.3.8 you can
  • get the latest screen capture app at:
  • http://btnet.svn.sourceforge.net/viewvc/btnet/www/btnet_screen_capture.exe

New in BugTracker.NET 3.3.8 (Aug 19, 2010)

  • 3.3.7 was accidently zipped with the wrong default Web.config. Too
  • much stuff was enabled by default, and there were email settings in it
  • that caused some people some trouble.
  • Fixed bug 2945674 - Customized "SvnBugidRegexPattern1" doesn't work properly. Thanks to "superdaigo" for the fix.
  • Btnet_screen_captured.exe wasn't remembering to save the password.
  • Several enchancements to btnet_screen_capture.exe:
  • Ctrl-C copies contents to the Clipboard.
  • You can specify the projectid.
  • Draw straight lines with arrowheads.
  • Highlight with "yellow highlighter" in addition to free form red lines.

New in BugTracker.NET 3.3.7 (Aug 19, 2010)

  • The only that changed in this release is the screen capture utility.
  • Completely rewrote the BugTracker.NET screen capture utility. It's
  • now version "2.0". Here's the story: Several years ago I wrote a
  • screen capture utility and it was Ok. Then Alexej Hirsch developed a
  • really nice app, "Bug Shooting", that works great with BugTracker.NET
  • and several other bug trackers. I abondoned my own app and started
  • using and recommending his.
  • But just this week, Alexej switched Bug Shooting from being a free app
  • to being shareware with a 30-day trial. I wanted my BugTracker.NET
  • users to have something free, but my old app from several years ago
  • wasn't that nice, and, it was built using C++ and MFC rather than .NET.
  • It's just harder to work with those tools than it is with .NET, and
  • I wasn't eager to return to that codebase to improve my old app.
  • So, I started over, using C#/.NET and Visual C# 2008 Express Edition,
  • which is free. The source is in the "screen_capture" folder and the
  • exe is in the www folder. Bugs.aspx incldues a link to the exe.
  • If you already have Bug Shooting, there's no reason to switch to my
  • app - Bug Shooting is still nicer, but if you have my old app,
  • btnetsc_2.1.1.exe, you should switch to this new one.

New in BugTracker.NET 3.3.6 (Aug 19, 2010)

  • Reverted back to an older Lucene.Net.dll (the full text search). The
  • somewhat newer one was not compatible with GoDaddy's medium trust
  • setting. I'm using Lucene.NET 2.4.0, svn revision 829685. I built
  • the dll myself using the free VS C# Express 2008.
  • I also tried to fetch and build a Lucene.Net.dll from the
  • latest Lucene.Net source, but its interface has changed a lot.
  • Made the ad-hoc query page, "query.aspx", a bit easier by adding
  • a dropdown listing the db tables.
  • Fixed missing line breaks in notification emails.

New in BugTracker.NET 3.3.5 (Aug 19, 2010)

  • Added ability to change a custom columns default value.
  • Added "install_btnet.cmd", a quick and dirty install script. All I
  • can say is that it works for me, on my Windows 7 Pro machine.
  • Fixed bug where multiple svn/hg repositories were being used and
  • there was an overlap with revision numbers. The insert of revisions
  • was wrongly being skipped.
  • Fixed a cosmetic defect in the side-by-side diff. The first lines
  • were wrongly indented.
  • Fixed another cosmetic defect in the side-by-side diff. The changed
  • chars weren't always marked with orange.

New in BugTracker.NET 3.3.4 (Aug 19, 2010)

  • btnet_service.exe now looks for btnet_service.exe.config in the same folder as the exe, not in the c:\root folder.
  • For the svn, git, and mercurial integration, improved the diff page. The logic does a better job of coloring lines that changed yellow, and also colors the characters that changed orange. Also, the display of wide files works better (although I wish I had a splitter...).
  • Moved from jQuery UI version 1.6rc2 to version 1.7.2

New in BugTracker.NET 3.3.3 (Aug 19, 2010)

  • Fixed bug where deleting a user showed a SQL error with
  • bug_user_flags. Deleting a user was broken by changes in 3.3.2.
  • Fixed the $SEEN feature. It was broken by changes in version 3.3.2.
  • The exes for btnet_console.exe and btnet_service.exe were missing from
  • the zip file in version 3.3.1 and 3.3.2. They are back now.
  • If you use the bugid#123 feature to create hyperlinks between bugs,
  • these are now listed on the edit bug page, as "Linked to:", to make
  • these links easier to see.
  • Added a gently, only mildy annoying "nag" feature to, um,
  • encourage, organizations to donate. Only admins will see it. It
  • won't interfere with your work.

New in BugTracker.NET 3.3.2 (Aug 19, 2010)

  • To upgrade to this release, run the SQL for this release in the the upgrade.sql file.
  • Added a voting feature. It works like the $FLAG and $SEEN features. See the edit_query.aspx page for specifics, and see the "demo votes feature" sample query.
  • Fixed bug with the Web.config "UpdateBugAfterInsertBugAspxSql" setting. The name was one way in Web.config, a different way in the C# code. I made them the same. Thanks to Jorgen Sjoholm for this fix.
  • When you check "edit using fonts and colors", you are using CKEditor.
  • That has a spell checking feature that wasn't working well before, but
  • seems to be working better now, so I've enabled the CKEditor Spell-Check-As-You-Type feature this release. The change is just in the ckeditor/config.js file.
  • You can now use a regular express (regex) to control how the svn, git,
  • hg integration logic looks for the bugid in the checkin message. See Web.config.
  • Version 3.3.1 was missing the javascript for the nicer editor in the edit_query.aspx page.
  • Made the email fields a little longer in edit_user.aspx and edit_self.aspx.
  • The mercurial hook script no longer relies on the HG_NODE environment variable, so you can use it with events where that var isn't available.
  • Now specifying UTF8 when capturing output from svn, git, hg commands. It doesn't seem to hurt me, and it seems to have solved a problem for at least one user.

New in BugTracker.NET 3.3.1 (Aug 19, 2010)

  • Mercurial integration. It works the same as the integration with svn
  • and git.
  • Upgraded to version 3.0.1 of CKEditor. Performance seems better to me.
  • I re-arranged folders in my own subversion repository at sourceforge, and also in the zip file. All the web folders are now in a "www" subfolder. When you create a virtual directory, point it at the "www" subfolder, not the parent. I'm no longer using the sourceforge CVS repository.
  • Cosmetic improvements in edit_bug.aspx. Got rid of gaps between the links on the left, visible in IE only, in edit_bug.aspx.

New in BugTracker.NET 3.3.0 (Aug 19, 2010)

  • IMPORTANT - This release contains a reworking of the Subversion
  • integration. If you have already integrated BugTracker.NET with
  • Subversion, you will have a little bit of extra work to do when you
  • upgrade to this release.
  • Also, this release no longer supports the functionality of displaying
  • links to the php "WebSvn". If you were using that feature, contact
  • me at [email protected] and complain, so that I'll have some motivation
  • to add it back in.
  • The new svn hook script is subversion\svn_hook_for_btnet.py.
  • The old hook script made a connection to the BugTracker.NET database,
  • and so there needed to be connectivity between the subversion machine
  • and the databse machine. The new script does not connect to the
  • database. Instead, it posts an HTTP request to a new web page,
  • svn_hook.aspx, so your subversion machine will need connectivity with
  • the BugTracker.NET website.
  • I think for most people, this arrangement is easier, since the website
  • is typically already exposed, whereas the database is typically behind
  • a firewall.
  • Read the instructions in the hook script file itself. You will need
  • to edit some values in it just like you did with the old one. It will
  • be easy.
  • The hook script keeps track of what revision it last processed. The
  • first time it runs (or whenever it can't find the file that it uses
  • to keep track of the previously processed revision), it will send the
  • subversion log for all revisions to svn_hook.aspx. If you delete its
  • tracking file, it will send the entire log again. The Svn_hook.aspx
  • webpage is smart enough not to do duplicate inserts. Even revisions
  • where you forgot to add a bug id will still be inserted into the
  • revisions table, with a bug id of 0, so you could link them up to
  • bugs "by hand" yourself, with sql.
  • The revised web pages won't work with the data you currently have in
  • the svn_revisions and svn_affected_paths tables. You will need to
  • delete your data and let the hook script reload the data. It worked
  • fine for me.
  • Run this SQL to delete the data in those tables:
  • delete from svn_affected_paths
  • delete from svn_revisions
  • Then, when your hook script is working, delete "btnet_prev_revision.txt"
  • that it uses keep track of the previously processed revision, change
  • something, commit, and the two tables will get completely reloaded
  • with your entire repository log history.
  • The repository settings in Web.config and the project-specific svn
  • settings in Web.config are also gone, because the repository info
  • now is stored in the db. But, if a username and password is required
  • to read your repository, then you configure that in Web.config.
  • See Web.config for how to do that.
  • Run this SQL to get rid of the obsolete db columns:
  • alter table projects drop column pj_subversion_repository_url
  • alter table projects drop column pj_subversion_username
  • alter table projects drop column pj_subversion_password
  • alter table projects drop column pj_websvn_url
  • Finally, I apologize for the inconvenience but I think the new script
  • is better. It's more forgiving, because you can always delete your
  • database data and the script can be used to repopulate it. And, it
  • connects with the web server, not the database server. Finally,
  • because each revision is recorded along with the url needed to get
  • back to the repository, it's very easy to use multiple repositories
  • with one BugTracker.NET instance. Before I supported having a
  • different repository per project, but now you can have any sort of
  • scheme you want - even multiple repositories per bug.
  • Other changes this release are to the git integration:
  • Git integration was failing if file name contained spaces.
  • Even commits where the message does not contain a bugid are inserted
  • into the database, so that you could link them up to bugs "by hand".
  • I think pretty much everything I wrote above about the svn integration
  • also applies to the git integration. They both follow the same design.
  • The major differences are that with git, the repository MUST be on the
  • web machine, whereas with svn, the repository can be remote.
  • Would anybody use Mercurial integration if I added it?

New in BugTracker.NET 3.2.9 (Aug 19, 2010)

  • Git integration now complete. As with the subversion integration, you can use the "log", "diff", "blame" commands.
  • Your repositories need to be on the same machine as the web server. The hook script is git\git_hook_for_btnet.py.
  • Rename the extension to py. The script is written in python 2.X. Read the comments in it and follow the directions.
  • Edit the Git related settings in Web.config.
  • If everything is set up right, when you do a checkin, start the checkin
  • message with the bug id: git commit -a -m "123 fixed bug"
  • I'm not saying that the web pages related to svn integration were insecure, but I added a bit more security to them. You now can't view anything in svn via the web pages without the logic checking to make sure that you have permission for a bug related to the svn path.
  • Fixed a bug on the svn integration page where you can select any two revisions to diff. Sometimes the logic was getting confused and showed three revisions selected.

New in BugTracker.NET 3.2.8 (Aug 19, 2010)

  • Bug Fixes:
  • If you did a new install, not an upgrade, of 3.2.7, then you need to rename a field in your database using this SQL (og_domain_name should be og_name):
  • EXEC sp_rename 'orgs.og_domain_name', 'og_domain', 'COLUMN'
  • The file complete_registration.aspx should reference "SelfRegisteredUserTemplate" instead of "CreateUsersFromEmailTemplate".
  • The explanation of "UseEmailDomainAsNewOrgNameWhenCreatingNewUser"
  • was missing from Web.config.
  • New Feature. Integration with git. It's still under construction, but the ability to view revisions is working and so is the "diff" link. See the hook script in the git folder, and git settings in Web.config.

New in BugTracker.NET 3.2.7 (Aug 19, 2010)

  • Run this SQL to upgrade to this release:
  • alter table orgs add og_can_search int not null default(1)
  • alter table orgs add og_domain nvarchar(80)
  • alter table orgs add og_can_only_see_own_reported int not null default(0)
  • Added "can search" setting to orgs table, so you can turn off a
  • user's permission to search.
  • Added "can see only own reported bugs" setting to orgs table. If
  • checked, a user can only see the bugs that he reported.
  • Improved the handling of multiple embedded images in emails when the
  • embedded images have the same name. The new scheme no longer changes
  • the file extension.
  • Fixed bug where svn hook script was hanging if there were a lot of
  • files in the commit. Thanks to Richard Horton for the fix.
  • You can now resize custom field textareas by dragging them to a
  • bigger size.
  • The rest of the changes to this release are related to processing
  • incoming emails.
  • I've REMOVED a feature from this release, the feature related to the
  • Web.config setting "ProcessVariablesInEmails". This was a scheme that
  • allowed you to put magic words into the email body text to set a bug's
  • attributes. You can still put the magic words into the query string,
  • but not into email body.
  • I've added a new feature, though, that I think you'll like better, so
  • keep reading.
  • Again, this is the feature I REMOVED:
  • Added "domain", like "ifdefined.com" to orgs table.
  • Added new Web.config setting
  • "UseEmailDomainAsNewOrgNameWhenCreatingNewUser". In the same way that
  • you can allow incoming emails to create users, you can also allow
  • incoming emails to create organizations.
  • The logic checks if there is already an org with a domain that matches
  • the from-address of the email. If there is, the new user gets assigned
  • to that org. If the org doesn't exist, the system creates a new org
  • based on the template user's org.
  • The domain is used as the name of the new org. You can change the
  • name, but you probably want to leave the domain as is, so that if
  • another user from the same org sends an email, the new user is
  • associated with the same org.
  • Added new Web.config setting "UpdateBugAfterInsertBugAspxSql"
  • This lets you specify SQL that will run against the bug after
  • insert_bug.aspx has inserted it. Insert_bug.aspx is what inserts the
  • bugs that arrive from email and from the screen capture programs like
  • mine and "Bug Shooting". See Web.config for more info and some sample
  • SQL.
  • You could use this feature to automatically assign the bug to a
  • developer based on which org submitted it, for example. My sample
  • SQL in Web.config, just for teaching purposes, sets the priority based
  • on the email address of the sender.

New in BugTracker.NET 3.2.6 (Aug 19, 2010)

  • The SQL based search.aspx page wasn't working when the Lucene full text search was disabled.
  • Fixed bug where task's times were switched from PM to AM. Thanks to Philip Parmenter for the fix.
  • Fixed bug 2864901 "Embedded images in emails are saved to the same name". Duplicate file error when trying to forward MS Outlook with multiple embedded images.
  • Fixed validation of email address to allow apostrophes. Thanks to George Yiannitsaros for the fix.
  • There's an obsolete field in the database, which you are free to get
  • rid of: alter table bug_subscriptions drop column bs_id

New in BugTracker.NET 3.2.5 (Aug 19, 2010)

  • Fixed bug where nvarchar and nchar custom fields were allowing text to be entered with more characters than could fit in the db field.
  • If you are using the "news" link, enabled by setting "EnableWhatsNewPage" to "1" in Web.config, then this release should be an improvement for you. Now, if you keep the web page up, you won't loose news items even if you restart the IIS server. Also, you control the number of news items via the new "WhatsNewMaxItemsCount" setting in Web.config. Performance probably wasn't an issue before, but it's even less likely to be an issue now.
  • As before, news items are listed regardless of project and org permissions.

New in BugTracker.NET 3.2.4 (Aug 19, 2010)

  • send_email.aspx with CKEditor was broken. This release fixes it by
  • restoring the first line as:
  • Added setting to Web.config "StripDisplayNameFromEmailAddress" to
  • work around a problem that some users are having when email addresses
  • are in the format
  • Corey Trager
  • instead of
  • [email protected]
  • I can't reproduce the problem myself. see also bug 2815733, "When
  • sending mail to btnet, the mail address isn't correct"
  • http://sourceforge.net/tracker/?func=detail&aid=2815733&group_id=66812&atid=515837
  • If you want to maybe improve the performance of you BugTracker.NET
  • database a little bit, and I mean just a little bit, take a look at the
  • SQL in the file upgrade.sql for this release. The SQL mostly deals with
  • changing which indexes are the clustered indexes. If you don't
  • understand what that means, don't worry about it.
  • Performance tweak of viewing images, giving the browser a better
  • chance of caching them.
  • Fix of bug in edit_query.aspx, so that admins can now edit the queries
  • belonging to individual users.

New in BugTracker.NET 3.2.3 (Aug 19, 2010)

  • I made it a bit easier to customize BugTracker.NET if you are able to
  • code C#.
  • I revised the "workflow.cs" file. I really wonder if anybody could have been using the old workflow.cs? I was hired to do some BugTracker.NET customization for somebody and I myself couldn't get my own workflow.cs to work right.
  • If you are using workflow.cs, you'll have to rework your code to upgrade to this version.
  • See http://ifdefined.com/doc_bug_tracker_programmers.html#workflow
  • and the comments and sample code in App_Code/workflow.cs itself for
  • more info.
  • Full text search (Lucene) now also indexes custom text fields.
  • Fixed bug where full text search index wasn't always being updated when bug was changed.
  • I removed the SCAYT (Spell Check As You Type) from the rich text editor, CKEditor, because it was working so poorly and unreliably.

New in BugTracker.NET 3.2.2 (Aug 19, 2010)

  • Fixed javascript error in search.aspx that was preventing SQL from displaying when "EnableLucene" was set to "0" in Web.config.
  • Fixed bug with "FLAGS". The filtered state wasn't being preserved in the bug list when you navigated away and back to it.
  • Fixed bug 2821937 "NOT logic does not work for 'flag' field"
  • Fixed bug 2830310 "tags filter - only one result page can be used, filter remov"
  • Fixed bug 2821768 "sql editor in edit_report.aspx". Now using "EditArea" for edi_reports.asxp. See notes for previous version for more on "EditArea". Also, fixed bug with text being HTML encoded that should have been.
  • Added back the "CommentSortOrder" to Web.config. Controls whether bug posts are sorted from most recent to least recent (the default) or least recent to most.
  • Added "DisplayTimeOffsetInHours" to Web.config, for displaying the times in a different time zone than the server's time zone.

New in BugTracker.NET 3.2.1 (Aug 19, 2010)

  • send_email.aspx was broken in version 3.2.0 because it still
  • referenced FCKEditor 2.6. Fixed.
  • The list of email addresses you see when you hit the "To" button was lost if you had a validation error, like forgetting to enter a "To" address.
  • The page for editing your SQL queries now has syntax highlighting, using "EditArea", from http://www.cdolivet.com/index.php?page=editArea. Thanks to "Gettinlucky" for the suggestion.
  • "FromCannotContain" setting in btnet_service.exe.config wasn't working.

New in BugTracker.NET 3.2.0 (Aug 19, 2010)

  • Run this SQL to upgrade to this release:
  • alter table orgs add og_active int not null default(1)
  • Changed search.aspx form method from "GET" back to "POST" See 3.1.9 release notes too. So, now, wtill with IE8, clicking on a link in
  • search.aspx to drill down into a bug, and then hitting Back to get back to the list, results in "Webpage has expired". I don't really have a practical solution to this.
  • Tweaked the SQL I inject to enforce permissions, as described here:
  • http://sourceforge.net/forum/forum.php?thread_id=3318801&forum_id=226938
  • Thanks to Luca Pardo for the idea.
  • Switched the rich text editor from FCKEditor 2.6 to the newer CKEditor 3.0 RC
  • You can now set organizations to be inactive. It works the same as setting projects to be inactive. Users adding or editing bugs won't be able to see in inactive org in the dropdown, but existing bugs still assigned to that org will work ok.
  • Fixed bug where prompt wasn't being displayed if you tried to leave a "dirty" bug page after changing a dropdown.

New in BugTracker.NET 3.1.9 (Jun 24, 2009)

  • The "fix" in version 3.1.7 "Changed code to work around OnServerClick not working..." (see below) broke the way the project dropdown works in edit_bug.aspx. In this version, I revert back to the pre-3.1.7 behavior.
  • Changed search.aspx form method from "POST" to "GET" to avoid IE8 "Webpage has expired" message (but now there's an anti-xss false alarm. Sigh...)

New in BugTracker.NET 3.1.3 (Mar 2, 2009)

  • Fixed bug 2634870 - "edit_task.aspx crash if bug has empty assigned-to"
  • Fixed bug 2414881 "btnet_post_commit svn script makes erroneous posts". The post-commit script was associating the incorrect bugid with the the revision when the bugid wasn't entered with the checkin. I also improved the debug output.
  • Fixed bug 2446465 "subversion diff fails when comparing one-line files"
  • Fixed bug 2526512 "problems when subversion thinks file is binary"
  • Fixed bug with custom dropdowns of type char/nchar. The app was recording changes even when the user made no change, because of values being padded with spaces in the database.
  • Fixed bug with svn_view.aspx. It was displaying the source with my own copyright notice.
  • Fix for "Request is not available in this context" error for IIS integrated mode. Thanks to Per-Erik Stendahl for the code.
  • Added a subversion post commit script in python, for those who are running a subversion server on linux, etc.
  • Added tip for short description. If it's longer than the INPUT and you hover over it, you can see all the text.
  • The formatting of the links at the top of the page are now controlled by "menu_td" css class.
  • When replying to an email, and quoting the original email, blank lines are now inserted into the reply before the quoted email.

New in BugTracker.NET 3.1.2 (Feb 21, 2009)

  • Fixed bug when inserting a null into the qn_last_exception column of
  • the queued_notification table.
  • Fixed bug 2596624 - "Blank comment entered when using the rich text
  • editor".
  • Version 3.0.5 broke the features where BugTracker.NET records the
  • most recent login date of a user. Fixed in this version.
  • Corrected some typos in the hour dropdowns in the time tracking
  • feature.
  • Fixed [+], [-] links to resize rich text editing area.

New in BugTracker.NET 3.1.1 (Feb 9, 2009)

  • Fixed bug with "show images inline" when MIME type was pjpeg or x-png.
  • IE7 tends to use these MIME types.
  • Fixed bug: Custom fields rendered as textareas were getting
  • HtmlEncoded twice.
  • Fixed bug: Custom fields displayed in textareas lost their formatting
  • when displayed as read only.

New in BugTracker.NET 3.0.9 (Jan 26, 2009)

  • Fixed a bug with send_email.aspx introduced in version 3.0.8. Prior
  • to version 3.0.8, list of email addresses wasn't taking into account
  • the users organization permissions. I fixed that in 3.0.8 but broke
  • the logic related to project permissions. With this release, both
  • organization and project permissions should be working (I hope).
  • Updated included Web.config so that the session timeout is 120
  • minutes.

New in BugTracker.NET 3.0.5 (Dec 17, 2008)

  • To migrate to this release, run the SQL in upgrade.sql.
  • alter table orgs add og_can_view_tasks int not null default(0)
  • alter table orgs add og_can_edit_tasks int not null default(0)
  • Org permissions now include settings for "view tasks/time" and "edit tasks/time". They are OFF by default, so you might need to edit your org permissions if you have "EnableTasks" set to "1".
  • No longer supporting "CustomWelcomeHtml" in Web.config. Instead, put your custom HTML for the default.aspx into the custom_welcome.html file in the custom folder.
  • Added new Web.config setting "EnableRelationships" for turning that feature on and off. It is OFF by default, so if you were using it you need to add the line to your Web.config, and set it to "1".
  • Fixed bug where change history was missing from the emails. The bug was introduced in version 3.0.4.
  • Fixed bug where deleting of bugs was leaving behind the related tasks. Now deleting them.
  • Fixed bug where us_most_recent_login_datetime wasn't being updated if Windows authentication was being used.
  • Fixed bug where guest was seeing "add task" link, but wasn't allowed to add task.
  • Added to setup.sql a couple sample reports related to the new tasks/time feature.

New in BugTracker.NET 2.6.5 (Nov 22, 2007)

  • Cosmetic changes in the add/edit bug form. The goal is to make it easier to read for all three categories of users: full add/edit permission, reporter only permission, view only permission
  • In general, in the coming releases, I want to make BugTracker.NET better as a tracker that faces outside, customers, clients, users, rather than just a tracker that is used internally.
  • "Comment visible to internal users only" shouldn't have been visible to view-only users
  • In relationships page, "detach" link shouldn't have been visible to view-only users.
  • Hid links that view-only users shouldn't see: add attachment, send email