NetResults Tracker: Features (Enhancement) List - Web-based Bug Tracking, Issue Tracking, Workflow/Change Management, Knowledge Base, Customer Support and Help Desk

skip main navigation

Product

skip to page content

Tracker Features

Version 4.1.1

Enhancements

When configuring a set of Dependent Pulldowns in Version 4.1, if no relations were configured between the option menu items of the related pulldown menus, the Default Items section for the child pulldown would not show any implicit (temporary) default option menu item(s). This has been changed such that an implicit (temporary) default is displayed for each option menu item in the parent pulldown. Implicit defaults are denoted by {Default}. Explicit defaults are denoted by [Default]. More information is available in the Configuring Dependent Pulldowns section of the Online Help Document.

Fixes

When upgrading from Version 3.x to 4.x with the email notification for "On Add and Delete, notify..." set to notify only the Current State Manager, invalid information would be added to the "On Add, notify..." and "On Delete, notify..." rules after the upgrade. This has been corrected such that the upgrade will create both "On Add..." and "On Delete..." rules without invalid information.
In Version 4.1, when running a query and using the Edit Results operation to change a field which was part of the query criteria, history entries were not created for the affected records. This has been corrected such that the history entries are created in this situation.
When using the date clean up utility when upgrading from Version 3.x to 4.x with dd/mm/yyyy format, the user could be prompted to update system generated dates. This has been corrected to allow the date clean up utility to update the system generated dates without prompting the user.
In Version 4.1, when a user had set a saved group query as the default query and the user group was deleted, a system error would occur. This has been changed such that the saved group query "Default [Users]" will become the user's default query when the user group is deleted. Likewise, if a user has a saved group query as the default query and the user is removed from the group, the saved group query "Default [Users]" will become the user's default query.
In previous versions, if a group saved query was saved with a personal report layout, a system error would result when another user ran the group saved query and used the "Format For Printing" option. This has been corrected such that a system error will not be generated. Instead, the global default report layout ("Default [Users]") will be used to format the query results for printing.
When upgrading from a previous version to 4.1 with an attachment file that contained a single quote in the name, a system error would be generated. This has been corrected such that the single quote in an attachment file name can be upgraded properly without generating an error.
In previous versions, when the number of characters entered into a field with "BigText" format during the Add operation was over the limit for the database type (typically 64,000+ characters), a stack overflow error would be generated during the Add or Edit operations. This has been corrected such that the user will be prompted if the number of characters is over the limit before the new record can be added.
In Version 4.1, when restoring a deleted option menu item, the dependencies configured for the option menu item were not restored. This has been corrected such that when a deleted option menu item is restored, its previous associations to other option menu items are also restored.
In Version 4.1, if the option to "delete all records" was selected when deleting an option menu item, any attachment files associated with these records were not deleted. This has been fixed so that the corresponding attachments files are deleted with the records in this situation.
In previous versions, when multiple task fields shared the same sort order within a transition, the fields were not sorted in alphabetical order. This has been changed such that multiple task fields with the same sort order within a transition will be displayed in alphabetical order.
In Version 4.1, if a user has visibility to a field on the Query page and is using this field in a Saved Query and the user group that provided the user with visibility to this field is deleted, then the Saved Query was not updated to remove the field. This has been changed such that the user will be prompted that the Saved Query will be updated to remove the field (since the field is no longer visible to the user due to the user group being deleted).
In Version 4.1, if 2 or more columns were used to display Attachments or Source Code files in a report layout, the description of the files would not be displayed in every column when using the "Format For Printing" option. This has been fixed to allow every column to display the appropriate description.
While using Netscape 6.2 with Version 4.1, an uneditable space was added to the option menu item labels of dependent pulldowns. This has been corrected so that the extra space is no longer present when using Netscape 6.2 with dependent pulldowns present.
When using Netscape 6.2 with previous 4.x versions while editing an email notification rule, the Assignee was selected even if it did not previously exist in the rule. This has been corrected such that the Assignee is not selected when editing a rule unless it already existed within that rule.
When using Netscape 4.x with previous ProblemTracker 4.x versions to upgrade from ProblemTracker 3.x, if certain date "clean up" operations that required user intervention (such as correcting a date that was in MM/DD/YYYY format when system settings were for all dates to be in DD/MM/YYYY format) were performed, one of the tables used to enter corrections was not displayed. This has been fixed so that Netscape 4.x can be used for the upgrade operation.

Version 4.1.0

Enhancements

Field Level Visibility has been added, allowing fields to be displayed or hidden based on a User Group membership on the Add, Edit, View, Home, and Query pages as well as in Email.
ProblemTracker now supports multiple time zones. Each user can specify a time zone which they wish to use when entering or viewing date/time fields.
The ability to configure Dependent Pulldowns is now available, allowing the menu option items in a pulldown to be dependent on the menu option item selected in another (parent) pulldown. For instance, the value selected in a "product" pulldown can be configured to limit (specify) the list of items that will be displayed in a "component" pulldown.
The ability to sort reports (query results) dynamically is now available on the Query and Home pages. Just click on the column name in a report on the Home or Query page to sort by that column. Click twice to sort in descending order rather than ascending order.
ProblemTracker now supports the use of Oracle 9i as the database software.
ProblemTracker now supports the use of Oracle 8i or 9i database on the Sun Solaris platform.
ProblemTracker now supports the use of Microsoft Windows XP. However, it is only supported for evaluation purposes. Microsoft has designated Windows XP as a "desktop" operating system (not a "server" operating system) and as such has restricted the number of users that may access a web server at one time on Windows XP.
In previous versions of ProblemTracker, the User ID (username) was displayed in various reports (Query, History, Home, View) as well as in Email. Now, you can select the format to display a user's identity in reports and email. The available options are: User ID, First Name, Last Name, Full Name. Upgraded systems will default to User ID for backward compatibility. Newly added workgroups will default to Full Name.
The ability to task records listed in the Second Home Page Report is now available.
When configuring a task field for a transition, the record order listed for the field in the Define Schema will now be the default value for the order of the task field in the transition.
The ability to remove the history comment from being displayed in a transition is now available. When a user selects a transition which is configured such that the history comment is not displayed and there are no task fields, the record will be updated immediately after selecting the transition, thereby allowing the task operation to be completed in fewer steps.
The functions on the Workgroup Database Tools page have been moved into the Workgroup Management System.
Users can now select an Advanced Saved Query as the default saved query (the one which is selected by default when they click the Query icon).
The following Help sections have had new information added. New sections are marked with (*):

Installation Guide (*):
User's Guide:
Admin Guide:
Workgroup Management Guide:

Fixes

In previous versions, when using a date field as part of an Advanced Query, a system error would be generated. This has been corrected to allow the advanced query to run successfully with a date field present.
In previous versions, searching Text or BigText fields for key words using an Advanced Query was not returning the expected results. This has been fixed so that advanced query key word searches generate the correct results.
Starting in version 4.0, the values for the From Email Account and Send Email Account are swapped, meaning that the from account was being used as the send account and vice versa. This has been corrected.
In previous versions using Windows NT 4.0 as the server machine, attempting to block/unblock a workgroup via the Workgroup Management System was not successful. This has been corrected to allow the workgroup to be blocked/unblocked when ProblemTracker is installed on a Windows NT 4.0 machine.
In previous versions during certain instances, an attachment file upload would fail on a heavily loaded server (for example, when an application on the server is running with unlimited CPU), causing a timeout to occur and the system to no longer respond. This has been fixed such that the file upload will be handled in the case of a system with a heavily loaded CPU.
All system generated saved queries ("Default", "Assigned To Me [Users]", and "Reported By Me [Users]") will now exclude soft-deleted records (those that are not actually deleted from the database). This change may affect system generated saved queries in upgraded installations as well as new installations.

To read about the features in Version 4.0 - 4.0.3, click here.