Now AQdevTeam Server supports Microsoft Internet Information Services (IIS) 6.0, which is part of Windows Server 2003.

Full text search improvements:

• Now search indexes can be configured in AQdevTeam Server, using the AQdevTeam Server Properties dialog. See the AQdevTeam Server documentation.
• Now you can select several projects and item types in which you want to perform the search (See Full Text Search Criteria Dialog). In previous versions, you could search either in the entire database or in one particular item type and project.

Instead of creating events for items, now you can easily set up the email notification policy for an individual item directly within the Edit Form. To do this, a TAutoNotification control should be placed onto the Edit Form. TAutoNotification encapsulates several controls that let you specify which item fields AQdevTeam will track for changes and which users you want to sent email notification messages automatically.

Now administrators can temporarily "disable" users existing in the database. After a user has been disabled, they cannot log in to the AQdevTeam database. Later you can enable the desired user or keep them disabled. Enabling and disabling users solves the issue that occurred when users connected to the database in OS authentication mode. Previously, to forbid a user access to certain projects or item types, you had to set user permissions for all of the projects and item types you wish to hide from the user. It was not enough to delete a user from the database, because the user could connect to it in OS authentication mode. Now you can simply "disable" the user and they will have no way to log in to the database.

Now you can create several projects with the same name, but different versions. In addition, you can create item types that have the same names. There are specific options that control whether or not you can do this.

In previous versions, you could only link items that were already saved to the database. Now if you open the Edit Form to create a new item, you can add links to the item even if it is not actually created yet.

The last entered value of an item field is now stored per item collection. Previously, it was stored per item type.

Clients' interaction with the server has been changed. Now AQdevTeam Server cannot be launched by a request from AQdevTeam Client or AQdevTeam Web Interface. This will help administrators to perform operations that require AQdevTeam Server to be switched off on the server computer. Previously, administrators may not have been able to perform these operations successfully since a user could start AQdevTeam Server.

AQdevTeam includes a new toolbar, Issue Explorer Quick Edit, with an edit box and a button on it. They allow you to quickly search for items. You specify the identifier the sought-for item has in the selected item type and press the button. Once the item is found, AQdevTeam opens the Edit Form with this item.

When you drag a file to the Edit Form in order to attach the file to the item currently opened there, the Attachments tabbed page is automatically brought to front. In addition, now you can attach files by dragging them to the Attachments page. Depending on the pressed key, AQdevTeam will attach either a file, or a file link.

The Group Properties dialog has been added. It lets you specify users that will be members of the given group.

Now you can easily format columns of the Issue Explorer panel. The panel's context menu holds a new item, Format, that opens the Format Columns dialog. Here you can specify the font, color, style and sorting order for the selected column.

A new built-in routine, NamespaceExists, lets you easily determine whether an object exists. You can use this function, for instance, to see if an object supplied by an AQdevTeam plug-in is available (as alternative way to the NamespaceExists function is to use the exception handling code).

The UserManager.CreateUser method becomes obsolete. We recommend that you use the new RegisterUser method for creating new users. CreateUser is supported for backward compatibility only.

The User object has a new property - Enabled. It lets you disable or enable a user from your scripts.