This file lists the defects fixed since the last major release of Tracker. For information on installing and using the current release of Tracker, see the <Install_Directory>\Tracker\readmetr.htm file.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed, and the readme now lists Oracle 10g as a supported database.
If IUSR does not have write access to the LDAP information file, LDAP authentication fails. This has been fixed.
This has been fixed.
If a specific port is specified for the license server during installation, Tracker adds an extra @ character in pvcstrk.ini.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed for 8.x projects.
If a user who has not used the In Tray for a long time opens the In Tray, the resulting In Tray notifications can cause SQL Server to crash.
This has been fixed.
If a user who does not have any existing notification rules (not even a rule for the Public group) adds a new rule, Tracker crashes.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
When you try to close a parent issue while its child is still open, the resulting error message reports the wrong issue ID. This has been fixed.
Users with Oracle databases receive an " Out of Memory" error during the upgrade. This has been fixed.
This has been fixed.
Now, when checking in a file or adding one to source control, you can automatically assign a version label that contains the Tracker issue number using TrackerLink.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed; the "free" statement in the Tracker Administrator's Guide has been deleted.
This has been fixed.
When you view only the last note in an issue (rather than all notes), Tracker display's the first note's data. This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed. The message now reads, "These changes may not take effect if this record uses a style sheet defined by an issue type."
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed; the Print Options and Print Preview menu items are now disabled if there are no records in the summary list.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
The text discussing single sign-on that appears in the Tracker Administrator's Guide should have "application" instead of "project". This has been fixed.
This has been fixed.
This has been fixed.
Running Verify and Repair with all options selected removes all new (Tracker 8) notification and escalation rules. This has been fixed.
This has been fixed.
If an anonymous user performs a submit, logs off from the project, and then submits to another project without closing the browser, the form from the first project comes up. This has been fixed.
This has been fixed.
This has been fixed. Relative dates are now always based on the day rather than on the time of day.
This has been fixed.
If you import a file with options under the State field other than Open or Closed (such as Pending), the import fails. This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
With LDAP enabled, Tracker ignores the password field for user "admin". This has been fixed.
On Windows 2000, when you use the keyboard to make a selection from a choice field's context menu, Tracker does not retain your selection. This has been fixed.
This has been fixed.
This has been implemented: You can now check or uncheck a "show paperclip" option in the Select Columns dialog box.
This has been fixed.
The IUSR account requires read/write access to the root of the %SYSTEM% drive (normally C:/). This has been fixed.
This has been fixed.
Issue Type doesn't work correctly as a parent field. This has been fixed.
This has been fixed.
This has been fixed.
The documentation has serverName& instead of serverName$ in two places. This has been fixed.
The documentation has "Microsoft Development Environment." This has been fixed.
When a user using Tracker on Oracle 9i logs out of a project, Tracker errors out and continues to error out each time the user tries to open the Oracle 9i project. This has been fixed.
When you check out a file from the root of a project database in Version manager from within Tracker, you receive a runtime error and an abnormal program termination. This has been fixed.
According to the schema, the noteMdDate is the date and time when the note was last modified, but there is no user interface to display this value. When you modify a note on a record, this value does not change.
This has been fixed.
Customer was experiencing deadlocks. When the Tracker trkproc table is updated frequently, it caused deadlocks without giving messages to the user to let them know. This has been fixed.
When you use TrackerLink or Module Associations within Tracker, the path to the archive in the module association gets truncated if it is over 100 characters. This has been fixed.
The system requirements section of the Tracker Installation Guide directs users to a web site for the latest system requirements. This web site no longer exists. The system requirements are located in the readme file.
This has been fixed.
When a user pasted the license key string into the Merant License Manager from an e-mail message, the e-mail had changed the quote symbols and caused the license file to be corrupt for the license manager. This has been fixed.
When a user modifies a quick view report using the context menu, Tracker crashes. This has been fixed.
When you use the version management integration to check in a file that was not checked out by Tracker, the operation crashes. This has been fixed.
Module associations still occur in TrackerLink even when the file is not modified or checked in. This has been fixed.
When there are null rows in the trkfld table where the fldtypeID = 0, verify repair does not report the error. This has been fixed.
It is not possible to switch VM project databases from within Tracker's version management integration without logging out and then back in to Tracker. This has been fixed.
Customer received an error stating "The memory could not be read" when using Tracker 7.x with terms containing high-ASCII characters. This has been fixed.
The online help for this dialog box is not visible from the dialog box. This has been fixed.
When using TrackerLink through the VM web client, the user receives the "Unable to get value for Title" error message. This error occurs when X5 column and the ID column in the trkscrsl table do not match and when the user performs an update by selecting the issue from within the Workfile Association dialog box. This has been fixed.
When users modify previously saved export sets in Tracker and exit Tracker without saving changes they made to the export set, the changes are saved. This has been fixed.
The "#" is being interpreted as a JavaScript symbol and causing this behavior. When a document is saved with "#" in the file name it changes to "log+#+2_doc.html". This has been fixed.
If a group name exists alphabetically before "Administrator", the first row is selected by default when you modify a user. This has been fixed.
When you use Tracker's version management integration to check in or out a file with no revisions associated with it, Tracker exits abnormally. This has been fixed.
The associated X on the upper right hand corner of the Update screen acts like the Cancel button. Tracker does not save any changes made to the issue until the OK button is clicked. If you click the X in the upper right corner, you will loose any changes. This has been fixed.
When performing the verify and repair action if trkscrsl and trkscrst tables do not have the same number of items, the user gets the following error: "The column prefix 'trkscrsl' does not match with a table name or alias name used in the query. Either the table is not specified in the FROM clause or it has a correlation name which must be used instead." This has been fixed.
In the Tracker Admin, the Report Assistant does not launch if the customer is using the Oracle Wire Driver for a server definition. This has been fixed.
Performance problems were reported when the customer was using keyword searches in the Tracker web client. These performance problems have been fixed.
If a SQL error happens during the submit or update, then the description text will be duplicated in the description after the second successful submission attempt. This has been fixed.
Tracker User Guide did not mention that a query with multiple keywords containing several fields and notes will not report records that have all of the words spread over the title, description, and note(s). This has been fixed.
There is no longer a TRKTOOLW.DLL file; it has been replaced by the TRKTOOLN.DLL file. The error was in the Tracker Toolkit documentation, which referenced the usage of the Basic call function in 16-bit. This has been fixed.
The user is not appearing in the drop-down list for owning a record. This has been fixed.
The dependent field relationship is a parent choice field and a child user field. If one of the child user groups is deleted, suddenly all user choices are available to all the choices in the parent field. This has been fixed.
The Tracker Administrator's Guide states the incorrect supported version of the SQL Server. This has been fixed.
Users are unable to install the Tracker Web Client Applet if they do not have Admin rights to their systems. This has been fixed.
When you export issues from one Tracker project to another, attached files are not exported. This has been fixed.
The Tracker User's Guide does not state which version of the Version Manager Development Interface you must install in order for TrackerLink to store revision numbers. This has been fixed.
When you log in to Tracker Admin using the Network installation and either the Oracle Wire or Client ODBC drivers, performance is slower. This has been fixed.
When using Tracker 7.5 with the 4.1 ODBC drivers, users find performance considerably slower on Tracker and Notify. This issue is fixed, and the performance is improved.
When you log in to an Oracle project, the User table is selected multiple times.
Verify/Repair was updated to repair this problem. This issue has been fixed.
When you build a query in I-Net using a field with a large number of choices, Tracker produces the error "Unable to open PVCS Tracker." This has been fixed.
When you copy a field from one project to another with the "Replace" option, the field is not replaced in Tracker. This has been fixed.
When you use a full-screen display with Tracker 7.1.1.0 on Windows XP and click a choice from a drop-down menu with many selections, the selected field and drop-down menu disappear, yet the entry is made. This has been fixed.
If "System Note Titles" is turned off in Tracker Admin, no project note titles appear when you export or import records. This has been fixed.
Importing records in common format does not work when "Title" is the last entry. This requires a workaround of not placing Title as the last field when exporting.
This has been fixed.
When you import records in Tracker that have the description as the last field, the record imports successfully, but the description field is left blank with no error messages given. This has been fixed.
When you install Tracker 7.1.10 from a shared network drive where users have read and execute permissions only with the "run from network location" option selected, the installer creates a local c:\program files\tracker\nt directory structure but no executable files. This has been fixed.
When a string field is set to required at close on the Submit and Update forms, the record would close without the required field filled in if the user accessed the record to close it using Actions | Update | State instead of using the Update form. This has been fixed.
After updating a module in the Association Modules list, users were brought back to the top of the list. This made it hard for users who had a large number of associations in the list to update. This has been fixed.
In previous installers, MDAC was a separate component item within the ODBC section, so users could choose whether to install it. Tracker 7.1.10 forces you to install MDAC 2.7.
This has been fixed. MDAC is once again an installation option.
Intermittent slower performance prevented users from using Tracker I-Net to its full capacity. This has been fixed.
When you use TrackerLink on the I-Net and the options "All Users" and "Show association dialog on checkin" are set, the association is ignored. This has been fixed.
A user was unable to perform an update on a record if their style sheet was set to <<Default>>. Instead, Tracker would lock the record. This has been fixed.
The PVCS Tracker Installation Guide contains a link to a Merant web site. The link is no longer valid. It provided system requirements and database information to users. This information is available only in the readme file.
This has been fixed. Please refer to the readme for system and database requirements.
Tracker I-Net does not display query fields for custom query windows when Rational Rose is also installed. This has been fixed.
The Tracker Report Metric did not display the Distribution report in table format correctly. This has been fixed.
If you first perform a network or workstation installation, you are then unable to install the I-Net portion later. This has been fixed: There is now a component in the installer allowing you to perform the network installation after you install the I-Net client.
When you send a manual e-mail notification, an empty dialog with a circle and red "X" appears. This has been fixed.
When you use hot keys to change from a field in which the first letter in the choice matches the destination location of the hot key, the choice in the field changes prior to the jump to the hot-key destination. This has been fixed.
When you try to upgrade projects from pre-7.1 versions to version 7.5, an error occurs stating: "Database error - NULL statement handle sqlExecDirect" and "[Microsoft][ODBC Driver Manager] Connection not open". This has been fixed.
After initially opening an attachment from an SCR, attempting to open that document a second time results in a blank screen. This has been fixed.
When SMPT is the configured e-mail server for Notify and attachments are included in notifications, the attachment was "shoved" into the text of the message. This has been fixed.
When multiple projects are open in Tracker, not all Global reports and trends from projects other than the current project would be visible in the Select Global Trends dialog. This has been fixed.
When you use Tracker with an NFS product, a decrease in performance can occur due to HTML file generation. This has been fixed.
TrackerLink was not associating workfiles if the user account was password protected. This has been fixed.
When users try to import data from other sources into Tracker, they receive errors and are unable to complete the operation. This has been fixed.
Users wanted the ability to display revision information in a pull down list for module associations in Tracker. Previously, users would need to go to Version Manager to see what revision information exists for an archive and then return to Tracker to associate it. This has been fixed with Tracker's version management integration. See the PVCS Tracker User's Guide for details on integrating versioning information with Tracker.
In Tracker I-Net, when SCRs are updated and submitted in a project and then the same project has custom fields added to it in Tracker Administrator, the updated and submitted SCRs produce an error. This has been fixed.
Tracker I-Net fails after login with 3rd party product from Sun. This has been fixed.
When you run a change history query and specify changes to the Owner field, Tracker returns an "ORA-00907: missing right parenthesis" error. This has been fixed.
Workstation installation with a modified pvcstrk.ini file in the tknt directory does not get copied to the workstation whether or not an existing file exists in the %system_root%. A new one gets created, but does not contain modified contents from the copy in the tknt directory. This has been fixed. Refer to the PVCS Tracker Installation Guide for information on setting up a silent installation.
When Notify is running using newer versions of Microsoft Outlook or older versions with a security patch, upon each attempt to send e-mail, it will ask you "A program is trying to send e-mail on your behalf. If this is expected behavior, click Yes." Use the following workarounds:
Use SMTP protocol. You need to be careful to use an e-mail name that works correctly in all the mailers where it will be used.
Register certain executables at the Outlook Exchange server to allow them to send e-mail.
In the Tracker GUI, set the "Preview Message" option. While you are using a Microsoft mailer, the preview option will slow down the message sending operation long enough to make the message unnecessary.
The TrkPerm schema documentation does not include the two bits for Import New Users and Override Field Mappings. This has been fixed: These two bits have been added to the Tracker Admin Schema documentation.
The Logging In topic contains confusing language. This has been fixed.
There is a misspelled word in the Query by ID dialog box in Tracker I-Net. This has been fixed.
If a file is checked out and back in through Version Manager, Tracker has no record of it. In earlier versions of Tracker, you could associate a new revision with the SCR. Now, Tracker associates the entire module with the SCR instead of associating a particular revision, but it's hard to tell which revision fixed that SCR.
This has been remedied with Tracker versioning integration. See the Merant Tracker User's Guide for details on versioning integration.
In the Tracker Administrator help, the "More Information" pop-up window comes up blank. This has been fixed.
End Release Notes
Copyright © 2003–2004 SERENA Software, Inc. All rights reserved.
$Revision: 1.70 $