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

Product

NetResults Tracker Fixes

Version 6.0.1

Fixes for issues in Version 6.0.0
PRN 4390	A system error would occur when selecting "<No Report>" as a replacement for Home Page reports when deleting a user group. This has been corrected such that "<No Report>" can be selected for any Home Page report (including the First Home Page report) without causing a system error.
PRN 4397	A single quote in the label of an option menu item would be displayed as two single quotes. This has been corrected such that a single quote in the option menu item label will be displayed correctly.
PRN 4398	A few internal links within some of the Help Manuals were not correct, resulting in "not found" errors. This has been corrected such that the links display the appropriate sections without error.
PRN 4439	When Text and HTML option was selected in the Outgoing Email Configuration, the <action user> variable did not display the user's name in email notification messages. This has been corrected such that the actual user's name will be displayed properly with the Text and HTML option enabled.
PRN 4440	When any of the variables <old assignee>, <new assignee>, <old status> or <new status> were included in email rules for "On Add" and "On Delete", the actual value of the variable was not replaced in the email messages. This has been fixed such that the actual value is displayed correctly.
PRN 4443	If (a) a user account was in more than one workgroup and (b) was deleted in one of the workgroups and (c) that workgroup was the first workgroup to which the user was given access, then Edit operations on that user performed from the User Management System (UMS) would partially delete the user from the workgroup. This has been corrected such that the user can be edited using UMS without issue.
PRNs 4454, 4460, 4461, 4474	When a state was removed from a workflow, (a) properties of transitions in other workflows were being affected (instead of only affecting the workflow where the state was removed) and (b) the state was not being replaced in transitions with New Assignee set to "Last Assignee for State"; both (a) and (b) result in invalid state references. This has been corrected such (a) only the appropriate workflow will be affected and (b) the state will be replaced (or the transition deleted) when the state is removed from the workflow and will not affect. A Maintenance utility has been included to correct any invalid references in workgroups upgraded from Version 6.0.0.
PRN 4456	When using Firefox browser to submit a record on the Submit Page and the state manager of a field is based on a pulldown set to be displayed as a radio button, a system error will be displayed when trying to add a record using the Submit Page. This has been fixed such that a record will be submitted and a system error will not be generated.
PRN 4462	A saved chart would return the incorrect output if (a) the workgroup had multiple forms, (b) pulldown fields were added to one or more forms in a different order (the time when the field was added to each form), and (c) the chart was configured to breakdown calculations by a pulldown field other than Status, Assignee or Product. This has been corrected such that saved charts will return the correct output.
PRN 4464	A "Page not found" error would occur when clicking on a user information link on the Home Page after editing a record. This has been corrected such that the user information will be displayed as expected.
PRN 4467	A system error would occur when attempting to attach a file with a single quote in the name on the Submit page. This has been corrected such that an attachment with a single quote in the name can be attached without error.

Fixes for issues upgrading from Version 5.x to 6.0.0
PRN 4374	In some cases a default entry for Alerts in the Manage Workflows section would be missing (displayed as "<None>"). This has been corrected for those cases such that "Set Alert: No" will be displayed instead of "<None>".

Fixes for issues upgrading from Versions 3.x, 4.x or 5.x to 6.0.0
PRN 4442	If a transition was set to use Product as a Task Field prior to the upgrade, the Product field was not displayed during the Task operation, the Product field was not listed in the In Use column and no fields at all were listed in the Not In Use column when editing Task Fields and a system error would occur when attempting to edit the transition. These issues have been corrected such that Product is displayed as a Task Field, fields are displayed as expected when editing Task Fields and the transition can be edited without error.

Fixes for issues upgrading from Versions 3.x, 4.x or 5.x to 6.0.0

PRN 4442

If a transition was set to use Product as a Task Field prior to the upgrade, the Product field was not displayed during the Task operation, the Product field was not listed in the In Use column and no fields at all were listed in the Not In Use column when editing Task Fields and a system error would occur when attempting to edit the transition. These issues have been corrected such that Product is displayed as a Task Field, fields are displayed as expected when editing Task Fields and the transition can be edited without error.

Fixes for issues in Versions 4.x, 5.x and 6.0.0
PRN 4446	When running a Query using the "AND Before" field, the query would match those records with a date value that exactly matched the Before field to the second. This has been fixed so that it only matches those records with a date value that is one second before the Before field value. So, for instance, if the Before field value was 07/11/2007 2:00:00 PM (July 11th at 2 PM), the query would improperly match records where the date field had the value 07/11/2007 2:00:00 PM, when it should only have matched those records where the date field was 07/11/2007 1:59:59 PM or earlier. Since Date fields without a time component are treated as if the time component is midnight, a Before field whose value was 07/15/2007 (equivalent to 07/15/2007 12:00:00 AM) could have matched a record with a date value of exactly midnight on July 15th (07/15/2007 12:00:00 AM or 07/15/2007). Now it will only match records with a value one second before (in this example, 07/14/2007 11:59:59 PM or earlier).

Fixes for issues in Versions 4.x, 5.x and 6.0.0

PRN 4446

When running a Query using the "AND Before" field, the query would match those records with a date value that exactly matched the Before field to the second. This has been fixed so that it only matches those records with a date value that is one second before the Before field value. So, for instance, if the Before field value was 07/11/2007 2:00:00 PM (July 11th at 2 PM), the query would improperly match records where the date field had the value 07/11/2007 2:00:00 PM, when it should only have matched those records where the date field was 07/11/2007 1:59:59 PM or earlier. Since Date fields without a time component are treated as if the time component is midnight, a Before field whose value was 07/15/2007 (equivalent to 07/15/2007 12:00:00 AM) could have matched a record with a date value of exactly midnight on July 15th (07/15/2007 12:00:00 AM or 07/15/2007). Now it will only match records with a value one second before (in this example, 07/14/2007 11:59:59 PM or earlier).

Version 6.0.0 Patch A

Fixes for issues in Version 6.0.0
PRN 4406	Records that were soft deleted were being displayed for selection in Link Fields. This has been corrected such that soft deleted records will not be available for selection in a Link Field.
PRN 4410	A system error would occur when using a Link field on Knowledge Base pages. This has been fixed such that Link Fields can be used on Knowledge Base pages without causing a system error.
PRN 4411	When using Link fields with a case-sensitive SQL Server database, a system error would be displayed when adding items to a Link field. This has been fixed such that a system error will not occur.
PRN 4413	A JavaScript Error would occur when using a Release Number as a required Task Field with a certain combination of option menu items in each digit of the field. This has been corrected such that a Release Number field can be set as a required Task Field without error.
PRN 4414	The focus did not always work properly when a Release Number field was used as a required Task Field. This has been corrected so that the focus works as expected.
PRN 4417	When using a case-sensitive SQL Server 2005 database, a System Error could be displayed when adding a Release Number field to a Form. This has been corrected so that a RelNum field is added without error.
PRN 4426	The "Task Records in State(s)" privilege was not being applied to a user group when the privilege "Task Assigned Records" was also enabled. This has been corrected such that the Task Records in State(s) privilege is now applied as expected.
PRN 4427	The "Value is Public" property was being ignored for Pulldown and Release Number fields. This has been corrected such that the items that have this property enabled will not be displayed on the Submit and Knowledge Base pages.
PRN 4430	When sorting a saved query by a Release Number field, only the first digit in the RelNum field was used. The value of the second, third, and fourth digits were ignored. This has been corrected such that all digits are used for sorting.
PRN 4432	If a saved chart (a) had an Input Filter value other than <All Records>, (b) the Input Filter (saved query) made a reference to the History Pulldown (Product), Assignee or Status field, (c) the saved chart was a trend (historical) Metric, and (d) the Input Filter (saved query) did not explicitly reference the Deleted field (this can happen if the Deleted field is invisible for the User Group associated with the saved query), then a system error would be displayed when the saved chart is run. This has been fixed such that the chart can be run without an error.
PRN 4435	O utgoing Email Rules which used a state group in their Condition were not triggered (no email was sent even if the condition was met). This has been corrected such that the email notifications are sent as expected.

Version 6.0.0

For a list of Features (Enhancements) in this version, please browse to the Version 6.0.0 Features list.

Fixes for issues in Version 5.5.x
PRN 3753	Incoming messages without a Reply-To account sent to a mail account to submit a record via email would not be processed. This has been corrected such that the message is processed even if the Reply-To field is empty.
PRN 3920	The fields on the Knowledge Base results page were not displayed according to the order field. This has been corrected so that the fields are displayed in the correct order.

Fixes for issues in Version 5.x
PRN 3307	A runtime error would occur when trying to print a report after clicking on an email link to a discussion. This has been corrected such that the report can be printed without the runtime error.
PRN 3535	If a User ID was created such that it was a sub-string of an existing User ID and these users were members of the same user group and email notification preferences were set to notify this user group on Add, Edit or Task, a system error would occur when attempting to send the notification messages. The same error would occur when a user ID containing a "." in the name and another user ID differed by only 1 character (e.g. john.smith and johnasmith). This has been corrected such that the notification messages will be sent without an error.
PRN 3727	A system error would occur when trying to reply to a discussion message with the original message and more than 5000 characters in the reply. This has been corrected such that no error occurs when replying to a discussion message.
PRN 3793	URL attachments and URL fields with the "#" character would result in a broken link. This has been corrected such that URL attachments and URLs entered into URL fields with a # will not result in a broken link.
PRN 3844	A system error during login would sometimes occur if 2 users logged in at exactly the same time (within a small fraction of a second). This has been corrected such that the system error will not occur.
PRN 3849	The option "Set Alert" was displayed (though disabled) on the Add Page for a user without any Alerts privileges. This has been corrected such that users without Alerts privileges will not see the Set Alert option on the Add Page.
PRN 3885	It was possible to select "-----Queries (std)-----" and "-----Queries (adv)-----" headings for Default Input Records in a saved chart, which resulted in a system error when saving the chart. This has been corrected such that the headings are not available for selection in the Default Input Records field.
PRN 3898	An error would occur when attempting to update the user profile information in a workgroup for a user added to any other workgroup where the database was not currently available/accessible. This has been corrected such that NetResults Tracker will not attempt to update workgroups that are not available/accessible.

Fixes for issues in Versions 3.x, 4.x and 5.x
PRN 3664	A system error would occur when a Query Name contained more than 40 characters. This has been corrected such that a system error does not occur when the Query Name exceeds the maximum number of characters allowed (50 characters is now the maximum for the Query Name).
PRN 3666	Option menu items were not displayed according to their order on the Item Dependencies page. This has been corrected such that option menu items are listed based on the Order value set for the item.
PRN 3675	All child pulldown option menu items were displayed irrespective of selection in parent pulldown when using the Add Similar operation. This has been corrected such that the child pulldown will only display the option menu items related to the item selected in the parent pulldown.
PRN 3743	A system error when browsing to the State Managers (Workflow Properties) section would occur when a single quote was present in a state name. This has been corrected such that an error does not occur when browsing to the State Managers section when a state has a single quote in its name.
PRN 3757	A system date was displayed in blank date fields when using the Add Similar operation. This has been corrected such that the blank date fields remain blank when using Add Similar.
PRN 3764	The error "applet not initialized" would occur when trying to run a grid line chart when only 1 record matched the criteria. This has been corrected such that the chart will be displayed without the error when only 1 record matches the chart criteria.
PRN 3875	An error would occur when adding a record using the SDK while using field names with a RelNum type field. This has been corrected such that the record will be added successfully.
PRN 4159	The wrong state manager was selected when a product name contained a single character and there was another product name that started with the same letter. This has been corrected such that the correct state manager will be selected.