This project is read-only.

BugTracker.NET 3.2.7

Rating: No reviews yet
Downloads: 181
Released: Oct 4, 2009
Updated: Oct 4, 2009 by ctrager
Dev status: Stable Help Icon

Recommended Download

Application BugTracker.NET 3.2.7
application, 1764K, uploaded Oct 4, 2009 - 181 downloads

Release Notes

Run this SQL to upgrade to this release:
alter table orgs add ogcansearch int not null default(1)
alter table orgs add og_domain nvarchar(80)
alter table orgs add ogcanonlyseeown_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:
Allow special text in incoming emails to set
a bug's project, category, etc.

The variables are:
<add key="ProcessVariablesInEmails" value="0"/>
  • Added "domain", like "" 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
insertbug.aspx has inserted it. Insertbug.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

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.

Reviews for this release

No reviews yet for this release.