Known issues

Additional steps related to link validity data migration can be skipped during the migration.

First occurrence: 7.0

Problem: When you migrate from version 6.x to version 7.x, the Interactive User Guide lists additional steps that need to be performed to preserve link validity assertions involving RM requirements. If you have link validity data, these additional steps need to be completed to ensure the link validity assertions are preserved. However, if there are no link validity assertions involving the RM requirements, you can complete the upgrade without performing the additional steps. Check that there are no link validity assertions. Skipping the link validity migration when there are link validity assertions causes all such validity assertions to return to the suspect status in the user interface. You can confirm there are no link validity assertions by running the rm-repotools rmExportLinkValidity repotools command to export the link validity data from JTS. If the system generates a CSV file with no rows that contain the URL of the RM server that is being upgraded, you can complete the additional steps in the Workaround section to skip the link validity migration.

Run the rmExportLinkValidity command to verify that there are no link validity assertions

Workaround: If there are no link validity assertions involving RM requirements as determined in Run the rmExportLinkValidityData command to verify that there are no link validity assertions section, follow the steps provided in.Repository tools command to export the Requirements Management application link validity data during migration

Attempting to open a new row for editing in a module might lead to a row being added that doesn't permit editing

First occurrence: 7.0.2

Problem: Within a module, if you open a new row by using the Ctrl+Enter (or Cmd+Enter on a Mac) command or use the Insert New Artifact option in the edit menu, the end result might be thatthe new row opens but does not permit editing.When this occurs, the newly added row is displayed without an ID and the content cell does not show with an opened editor.

Comments widget on a personal dashboard displays an incorrect label for the Configuration setting

First occurrence: 6.0.1

Problem: If a personal dashboard is migrated from version 6.0 or an earlier release to version 6.0.1 or later, and it contains a Comments widget for a project that is enabled for configuration management, the label for the Configuration setting is displayed as $viewlet.prefs.configuration instead of Configuration.

Workaround: Delete the Comments widget from the personal dashboard and then add it again.

Cross-server link target titles are not shown on the Changed Resources tab and in the Audit History view

First occurrence: 6.0.6

Problem: When you view cross-server links on the Changed Resources tab or in the Audit History view, the titles of the targets are not shown.

Workaround: To see the title, navigate to the target of the link.

Cross-server linking cannot identify link type URIs on other servers

First occurrence: 6.0.6

Problem: When you create a cross-server link, any local link types that can be used for cross-server linking are available. Currently, the client cannot identify which link type URIs are available on other servers, which means that you can create a link that does not have a matching URI on the other server and cannot be seen on that server until you create the matching URI.

Workaround: Ensure that all link types with URIs have a matching URI for all cross-server components.

Delivering a large number of change sets might take a long time

First occurrence: 6.0.4

Problem: When you deliver a very large number of change sets (typically over 100,000), the client can take a long time to marshal the selected change sets. This delay occurs after the first step in the wizard, when you select the change sets to deliver.

Workaround: Deliver the change sets between streams in smaller sets.

Diagram shapes are not highlighted for incoming cross-server links

First occurrence: 6.0.6

Problem: When you click links in the Links section of a diagram, the related linked shape is highlighted. This function does not work for incoming cross-server links.

Workaround: To link to diagram shapes, use outgoing cross-server links.

Download button is disabled when downloading a ReqIF file from a baseline

First occurrence: 7.0

Problem: If you create and export a ReqIF file from a definition in a baseline, the export function appears to successful but the Download button is disabled and the ReqIF file cannot be downloaded. In version 7.0, the ReqIF metadata is a part of the baseline and cannot be amended.

During an upgrade, the CRJAZ0554I timeout error might occur

First occurrence: 6.0

Problem: During an upgrade, you might receive the following error, which indicates a timeout issue: CRJAZ0554I Unable to get the necessary lock in 30000 milliseconds.

During the CSV import process, artifacts that were partially removed cannot be reinserted into a module

First occurrence: 6.0.1

Problem: When you import CSV files, you cannot reinsert an artifact into a module if the artifact was partially removed; that is, the base artifact reference still exists in the project. The import process is only intended for creating new entries or for updating attributes for an artifact that is already part of the module.

Workaround: To reinsert an artifact into a module, use the artifact grid in the web client.

Error message is displayed when delivering large change sets

First occurrence: 6.0.1

Problem: When you deliver a module containing large number of artifacts (approximately 20000) to a parent stream, the web browser is unable to handle the module structure and a generic error message is displayed.

Workaround: Use the Express delivery option to deliver the change sets.

Errors are displayed during TRS rebase operations if timeouts occurFirst occurrence

First occurrence: 6.0.1

Problem: If you perform a Tracked Resource Set (TRS) 1.0 or TRS 2.0 rebase operation on a large Engineering Requirements Management DOORS Next repository, you might receive an error stating that the rebase operation could not be completed successfully. The error does not always mean that the rebase operation failed. In some cases, the error is caused by a timeout.

Workaround: To examine the actual status of a rebase operation, go to the TRS management page, scroll to the Tracked Resource Sets Status section, and click Status Refresh to update the status of the operation.

Existing views might be formatted differently after migrating to version 7.0.1

First occurrence: 7.0.1

Problem: In earlier versions, if the existing views with the link column traceability attributes are formatted to display the attributes as values only, then the attribute values are displayed in a single line. After you migrate to version 7.0.1, these attribute values are displayed as one value per line.This is due to the Show one attribute per line option that is added in this release.

Filtering large numbers of artifacts across CLM products might be slow or time outFirst occurrence

Problem: If you filter data that involves other CLM products and that includes a large number of artifacts, the query might be slow or time out. This issue is more likely to happen when a large number of artifacts is filtered to a very small result set, such as fewer than 25 rows.

1. From the grid's Configure Page Settings drop-down menu, select the first item: Show 25 Rows Per Page.
2. Change this value to 200 rows.

Importing large or complex word documents might take a long time

First occurrence: 4.0.5

Problem: When you import large or complex Word documents, the import process might take a long time. The resulting folder or module might load slowly and be difficult to navigate. This happens because of the size and complexity that is involved in handling the Word documents. DOORS Next processes just a single Word import operation at a time to prevent concurrent imports from compromising server stability by consuming too much memory or processing time. If an import request takes a long time, other import operations get blocked. This is a limitation based on the design of the product. This is applicable for both import wizards: Import requirements from within a text document and Import a text document and convert to a rich text artifact.Importing a Word document into a folder or module as multiple artifacts by using the Import requirements from within a text document wizard might take longer and consume more resources. Also, importing a Word document as a single rich text artifact might also be affected due to large and complex documents. For example, if the document is large and complex, the result of the import might be difficult to view and edit in the rich text editor.

1. Navigate to Advanced Properties under the Configuration section.
2. Search the WordImport.MergeSections property.
3. Set the property value as true and click Save.
4. If a Word document with a large number of section breaks is being processed, you might need to restart the server.

Large change set deliveries on Db2 databases might fail with an SQL error

First occurrence: 6.0

Problem: Delivering a change set with over 45,000 items can fill the Db2 database transaction log space, and cause the delivery to fail with an SQL error. The following SQL error codes are logged in the Requirements Management (RM) server rm.log file: Error: SQLCODE=-1476, SQLSTATE=40506, SQLERRMC=-964. The default Db2 transaction log space is sufficient for change sets with 45,000 items, but log space must be increased for larger change sets.

Links between artifacts in DOORS 9 and DOORS Next Generation do not work as expected when configuration management is enabled

First occurrence: 6.0

Problem: When configuration management is enabled in DOORS Next Generation 6.0, links to artifacts in DOORS 9 do not work as expected because DOORS does not support configurations.

Workaround: Instead of linking, use Requirements Interchange Format (ReqIF) to transfer DOORS 9 requirements into specific DOORS Next Generation streams.

Page Up and Page Down keys do not work properly when you edit an artifact in Mozilla Firefox

First occurrence: 6.0

Problem: In Mozilla Firefox, when you inline edit artifact content in a module, the Page Up and Page Down keys do not work. When you edit artifact content in the full text editor, Page Up will page to the top of the document and Page Down will page to the bottom of the document.

Workaround: Use these techniques to move the cursor:

• Use the Up Arrow and Down Arrow keys to move up or down.
• While in-line editing, press Ctrl+Home and Ctrl+End to move to the beginning or end of the text.

The Alt+e keyboard shortcut does not insert the euro sign in the Module editor

First occurrence: 6.0

Problem: When you edit artifacts in the Module editor, typing the Alt+e keyboard shortcut opens the Add Existing Artifact dialog box instead of inserting the euro sign into the rich text.

Workaround: To insert the euro sign, hold the Alt key and type 0128 on the numeric keypad.

The clmhelp.war file and the updateSite.zip file for release 7.0.2 are unavailable for download

First occurrence: 7.0.1

Problem: The clmhelp.war file and the updateSite.zip file for release 7.0.2 are unavailable for download due to technical issues.

Workaround: You can install the KCCI.zip file on your intranet server to view the help locally. Click here to download the ELM702_KCCI_contents.zip file.For information about installing the KCCI.zip file, see the Installing help on an intranet server topic.

You cannot import requirements if their embedded resources are on a different server

First occurrence: 6.0.6

Problem: For security reasons, you can't export requirements if they have embedded resources from a different server. You can export only the embedded resources that are on the local system, such as sketches, storyboards, or diagrams.

Workaround: To export requirements with embedded resources, create the embedded elements on the local system before you export them.When you import requirements with embedded resources that are on a different server, the embedded elements resolve only if the user is logged in to the server that contains the embedded resources.

Displaying link columns in module views might cause slow response time or session timeout when using Db2 version 11.1

First occurrence: 7.0.1

Problem: If link columns are displayed in module views, you might experience slow response time or session timeout. This issue might happen when you use Db2 version 11.1 without a fix pack and due to slow execution of a specific SQL query.

Migration from version 6.x to version 7.x fails with an error message: No link validity content applicable to current DN server

First occurrence: 7.0.1

Case 2: Migration process is done correctly but fails with the error message mentioned in the Problem section. The migration process is done correctly and the correct JTS server and repotools commands are used. However, the process still fails with the same error message. This happens when the RM server has at least one component with link validity enabled but there are no link validity assertions made against any requirements on the RM server.As per design, the command cannot differentiate between the case where the wrong JTS server is used or the case where no link validity assertions exist. You can skip the link validity migration and resolve the issue by following the steps that are provided at: https://jazz.net/wiki/bin/view/Main/SkippingLinkValidityMigration. Verify that there are no link validity assertions involving RM requirements. Execute the rmExportLinkValidity repotools command against the JTS server. For example, on Windows, enter the following command: repotools-rm.bat -rmExportLinkValidity repositoryURL=https://host_name:port/jtsadminUserId=admin_user_id adminPassword=admin_password. For Linux, enter the following command: repotools-rm.sh -rmExportLinkValidity repositoryURL=https://host_name:port/jtsadminUserId=admin_user_id adminPassword=admin_password. For more information related to identifying the correct JTS server, see the Choosing the correct JTS server for the upgrade commands section. Substitute the JTS server URL in place of https://host_name:port/jts. The command logs in to the JTS server by using the credentials that are provided in the adminUserId and adminPassword arguments. Open the rmLinkValidityToFile.csv file that is generated and search for the fronting URL of the RM server. For example, if the fronting URL is https://clmwb.com/rm, search for that text in the file. If there are no search results, complete the steps that are given in Case 2.

Choosing the correct JTS server for the upgrade commands. If you have a single JTS server, you can use that JTS server URL. If you have multiple JTS servers, use the JTS server URL identified by the advanced admin property called Shared Validity Provider URL. This property is specified in the JTS server that RM is registered with. If no URL is defined for the property, then use the URL of the JTS server that the RM application is registered with. Ensure that this JTS server is upgraded to version 7.x and is running for the commands to run properly.

Anchor point connections cannot be changed by using keyboard shortcuts on a Turkish Q keyboard

First occurrence: 6.0

Problem: In a diagram, you can change the anchor point connections for a shape by using the keyboard. The following keyboard shortcuts are used for these actions: Ctrl+/ and Ctrl+\. A Turkish Q keyboard does not have the forward slash (/) and backslash (\) keys. Although you can create these characters by using Shift+7 and AltGr+* respectively, these key combinations do not work to change the anchor point connections

Workaround: On a Turkish Q keyboard, use Ctrl+ö and Ctrl+ç to change anchor point connections in a diagram.

A module template's duplication policy is shared across its templates

First occurrence: 5.0

Problem: f you create multiple templates on the same module with a different duplication policy, the duplication policy of all of the module’s templates will be changed to the duplication policy of the last template that you created or modified for that module. This is because the duplication policy is stored as a property of the module and not the module template.

Artifacts with only review comments are not included when you sort the Comments column

First occurrence: 6.0.4

Problem: This behavior occurs only in projects that are not enabled for configuration management. When you sort the Comments column to display artifacts with comments, artifacts that have only review comments are not sorted in the correct order. Only comments other than review comments are sorted as expected.

Audit history related to deleted comments is missing or incorrect after upgrading to the version 7.0

First occurrence: 7.0

Problem: If an artifact has comments, which were deleted in version 6.x, some entries in the audit history might be missing after you upgrade the repository to the version 7.0. The audit history shows that the comment was deleted, but it might not show a comment change before the delete.

Browser zoom in or out support

First occurrence: 6.0.6

Problem: You can set the zoom level of the browser by using the zoom in and zoom out feature. Adjusting the zoom level out will generally work, but in some instances the page's layout might not be maintained properly. Adjusting the zoom level in is supported to 200%.

Comparison report does not display multiple entries of change sets if you edit a specific artifact several times

First occurrence: 7.0.2

Problem: The change sets that are included in the comparison report are the ones used for the comparison. If you change an artifact, type, or folder several times, the last change set is the only one that is included in the list of change sets.

Configuration Administrator role is displayed instead of Configuration Lead role in configuration management enabled project areas

First occurrence: 6.0.6

Problem: After you upgrade IBM Rational® DOORS® Next Generationand try to add members in configuration management enabled project areas, the Configuration Administrator role is displayed instead of the Configuration Lead role. This is likely to happen because of the upgrade process.

Content that is saved as a file cannot be exported to and imported from CSV and Microsoft Excel files

First occurrence: 6.0.6

Problem: If you try to export content that is saved as a file, such as a PDF file, to a CSV or Microsoft Excel file, the exported file contains an empty row that specifies the artifact is there, but has no content because that format is not supported. Because the content is not exported correctly, it cannot be imported from the CSV or Microsoft Excel file either.

Cross-project linking between module bindings in non-configuration enabled project baselines are not visible

First occurrence: 7.0

Problem: In a non-configuration enabled project baseline, the artifacts at the other end of cross-project links are not visible. This happens as there is no global configuration context in which to find the artifacts.

Embedded images, artifacts, and content is not visible if it is imported into a project or component where it does not exist

First occurrence: 6.0.5

Problem: If you try to import embedded artifacts, images, and content that is not part of the configuration for the project or component where the import process is being executed, those items are not visible in the current configuration, and the following message is displayed: The resource for this embedded image no longer exists or is not visible in the given configuration.

Exporting modules into CSV or Microsoft Excel files only exports module artifacts

First occurrence: 6.0.4

Problem: When you export modules from a module view or from only a module structure, the export process does not include base artifact information. In the context of a module, the export options are intended only for module artifacts or bindings.To export artifact information into a CSV or Microsoft Excel file, you must export directly from a folder where the target is located.

Incoming cross-server links are not created for imported files

First occurrence: 6.0.6

Problem: When you import a file, any incoming cross-server links are not created.

Java 8 SR5 Fix Pack 5 through Fix Pack 10 is not supported as the runtime for CE/CLM applications on a Windows platform

First occurrence: 6.0.5

Problem: Continuous Engineering (CE) and Collaborative Lifecycle Management (CLM) applications on a Windows platform that run on Java 8 SR5 Fix Pack 5 through Fix Pack 10 encounter null pointer exceptions and might not be usable. Use Java 8 SR5 Fix Pack 11 (8.0.5.11) or later as the runtime.

Link validity decorations are not displayed in an artifact grid for references links

First occurrence: 7.0

Problem: Link validity decorations are not displayed in an artifact grid of a baseline for references links. This happens as there is no global configuration in which to fetch artifacts at the other end of the link.

Link validity returning to a previous state maintains validity assertions for RM but not for other applications

First occurrence: 7.0

Problem: In a global configuration enabled project, if you enable link validity between artifacts in two RM projects and assert the validity, any change between the artifacts changes the validity state to suspect. If you undo the change, link validity assertions of previous state are maintained. This is because the state of an artifact in DOORS Next is based on its content.

If you use global configuration and enable link validity between an artifact in RM and a test case in QM and change the title of the test case, link validity state changes. If you undo the changes, the test case reverts to a previous state and the validity assertions are not maintained as the validity here is based on the etag, which changes with each edit regardless of the content.

Link validity summary is not visible for baselines for DM or RM links

First occurrence: 7.0

Problem: When you use link validity in non-configuration enabled project and in DOORS Next baseline, work items or resources that are stored in other applications are not visible to the DOORS Next baseline.

Microsoft Visio VDX and VSDX file formats have limited or no support for uploaded file previews

First occurrence: 6.0.1

Problem: The Microsoft Visio file formats that are XML-based, such as VDX and VSDX, lack support for uploaded file previews. For example, the VDX format has no support for file previews. A possible workaround is to convert the file to a different, older Visio format such as VSD. VSDX files have limited support for file previews; they cannot be rendered as thumbnail images. This means that a preview is not available when embedding the file as an artifact, when performing rich hover, when viewing it in a module, or from reports on that artifact. The only support for VSDX files is for viewing the artifact in full-screen mode or directly opening the artifact in Microsoft Internet Explorer with the Visio plug-in installed.

Starting with the version 7.0.1, support for Microsoft Internet Explorer is removed. As a result, the Microsoft Visio file formats that are XML-based, such as VDX and VSDX, lack support for uploaded file previews. For example, the VSDX format has no support for file previews. A possible workaround is to convert the file to an older Visio file format such as VSD. The Microsoft Visio Compatibility Pack provides a command-line tool that can be used for conversion

No message is displayed when you try to create incoming cross-server links that already exist

First occurrence: 6.0.6

Problem: If you try to create an incoming cross-server link that already exists, the action fails but no explanation is provided.

Poor performance immediately after RM server is restarted

First occurrence: 7.0.2

Problem: Immediately after the RM server is restarted, performance might be poor until the application has fully populated all its caches.

Quick Search results do not correctly include artifacts that have a format of Diagram

First occurrence: 6.0

Problem: If you use the Quick Search feature to search for artifacts that contain a specific string, the search results do not correctly include artifacts that have a format of Diagram. Search strings that are part of the first or last word of a plain text label or search strings that are part of a rich text label are not found.

Symbols or special characters are not displayed in reports

First occurrence: 6.0.2

Problem: When you create reports for rich text artifacts that include symbols or special characters, the symbols or special characters might not be displayed in the report if the reporting font does not support them.

System-generated change sets are not included as module dependencies in migrated data

First occurrence: 7.0

Problem: In version 7.0, all prior changes to a module will be included as dependencies when delivering a change set with edits to that module. However, system-generated change sets that have been migrated from previous releases will not be included as dependencies, if those change sets contain only structural modifications.

Team Area members that have a role with baseline creation permission does not have 'Create Baseline' option enabled

First occurrence: 7.0

Problem: A member of a Team Area that has a role with the permissions to 'Manage Baselines' enabled, and is not a member of the Project Area that does not have the 'Create Baseline' option available. To avoid any confusion, CM related permissions related to stream, baseline, and change set should not be inherited into team area permissions.

Text searches do not support queries that include certain characters

First occurrence: 4.0.2

Problem: When you search for text by using a quick search, full-text search, or term lookup operation, the search results might be inconsistent if the query includes one of the following characters:( ) { } [ ] « » / : ; * ? ! _ – ” < > | & . , ‘ “This limitation is caused by the way that the Jazz Team Server search facility handles special characters.

The main TRS validation does not process selections content

First occurrence: 7.0

Problem: TRS validation cannot process selections content currently. The selection validation and repair are not integrated with the TRS validation and repair feature, which are shown in the admin UI. This means that the main TRS validation feature does not check and repair the configuration mappings information.

The Review Comments column is not displayed in printed module reports

First occurrence: 6.0.4

Problem: If you create a report for a module in a table format and the report includes the Review Comments column, that column is not displayed when you print the module report. The column is excluded because the printed version does not show the correct information.