This project is read-only.

BugTracker.NET 2.5.8

Rating: No reviews yet
Downloads: 125
Released: Oct 26, 2007
Updated: Oct 30, 2007 by ctrager
Dev status: -not yet defined by owner-

Recommended Download

Source Code BugTracker.NET 2.5.8 (with fix to add user)
source code, 1362K, uploaded Oct 30, 2007 - 125 downloads

Release Notes

To migrate from 2.5.7 to 2.5.8 run the sql in upgrade.sql.

IMPORTANT: This release affects user permissions and the behavior of
the search page. It's possible that some non-admins will temporarily
have FEWER permissions because I'm changing some settings to be from
global, for the entire installation, to per-user.

All users will be able to save searches as queries, but only users
you choose will be allowed to edit the raw sql.

Please keep reading for the details:
  • The following settings in Web.config are now obsolete. Instead
of the global switches here in Web.config, you can now control these
settings for individual users, which is explained in the next
bullet point:

  • The following fields have been added to the users page, permission tab.
Here's how they are explained on the page edit_user.aspx, in the
permissions pane:

Use the following settings to control permissions for non-admins.
Admins have all permissions regardless of these settings.
[] External user (External users cannot view posts marked
"Visible for internal usrs only")
[] Can edit sql and create/edit queries for everybody
[] Can delete bugs
[] Can edit and delete comments and attachments
[] Can merge two bugs into one
[] Can mass edit bugs on search page
[] Can use reports
[] Can create/edit reports
X Appears in "assigned to" dropdown in edit bug page (defaults to true)

Except for "Appears in 'assigned to' dropdown in edit bug page",
all the other fields default to false. That is, if you had any of the "Allow"
settings in Web.config set to "1", you will have to edit the user permissions
to restore the feature to that user. For example, if you had
"AllowBugDeletionForNonAdmins" set to "1", you will have to edit each user
and check "Can delete bugs".

You could also run some SQL to update settings for all users.
The format would be:
update users set XXX = 1
Replace X with one of the new fields:

The end result of removing the fields from Web.config and putting them
on the user page is that you now have finer-grained control over
who can do what.
  • All users by default now have the ability to save search criteria
as a private query that only that user can see. Users with
minimum permissions cannot see or edit the sql itself. Admin can
grant permission to individual users to see and edit sql, create
public queries.
  • Added new feature/concept: a distinction between internal and
external users. The feature is turned off by default. Enable
by setting "EnableInternalOnlyPosts" in Web.config to "1". When
enabled, acheckbox appears where you can add/edit comments
or attachments. The checkbox lets you mark the comment or attachment
as "Visible to internal users only". Users marked "external" on the
edit_user.aspx permission pane won't be able to see them.
Please read the entire comment in Web.config.
  • Added the ability to create a new user by copying an existing user.
Everything on the edit_user.aspx page gets copied except for the
source user's username, first and last name, password, email address,
and email signiture. All the permissions get copied.
  • Cosmetic change. The links to "edit" or "delete" things like users,
projects, categories have been moved from the far right to the far

Reviews for this release

No reviews yet for this release.