Workarounds and Limitations: Known issues in IBM Rational Quality Manager 5.0.1

The following known problems are related to Rational Quality Manager in the 5.0.1 release.

Workarounds

The following problems in this release have workarounds:

Limitations

The following problems do not currently have workarounds:


Workaround summary

Problem

This problem occurs on the Test Case Execution Records page and the Test Suite Execution Records page. If a saved query contains filters for categories and the results are grouped by an attribute, you cannot run the query. When you try to run the query, a message states Unable to load the content. Unterminated object at line/column: line 1, column 1.

Workaround

Complete these steps:

  1. Either clear the category filters or from the Group By list, select Ungrouped.
  2. Save the query and run it.
  3. Optional: After you run the saved query, reapply the group by setting or the category filters. However, do not save the query again.

Related information

Return to the top of the page


Workaround summary

Problem

When you use the Rational Quality Manager Mobile application, you might have difficulties connecting to the Quality Management server if the certificate that is used in your deployment is internally signed and not from a trusted certificate authority.

Workaround

Follow the detailed guidance on the Jazz.net wiki.

Related information

Return to the top of the page


Workaround summary

Problem

After you back up (repotools -backupJFSIndexes) and restore (repotools -restoreJFSIndexes), the test index, if you search QM artifacts, an error is logged in the Rational Quality Manager log:

com.ibm.team.repository.common.transport.TeamServiceRegistryException: CRJAZ2671E The "com.ibm.rational.test.lm.sequencer.service.internal.ExecutionSequenceInformationIndexingParticipant" service failed to activate because a service that it depends on, "com.ibm.rqm.common.service.IPagedSearchService", is not registered.
com.ibm.team.repository.common.transport.TeamServiceRegistryException: CRJAZ2671E The "com.ibm.rqm.execution.service.internal.query.ExecutionResultIndexingParticipant" service failed to activate because a service that it depends on, "com.ibm.rqm.common.service.IPagedSearchService", is not registered.

If any changes were made to the QM artifacts since the text index was backed up, they are lost.

Note: This issue impacts Execution Schedule and Execution Result artifacts.

When this issue occurs, artifacts are not in the full text index. You use that index when you search for QM artifacts from the search field in the upper-right corner.

Workaround

To retain the changes that were made to the QM artifacts since the text index was backed up, rebuild the text index by running this command: repotools -rebuildTextIndices.

Related information

Return to the top of the page


Return to the top of the page


Return to the top of the page


Return to the top of the page


Return to the top of the page


Return to the top of the page


Return to the top of the page


Problem

Typically, you can create an execution variable without a predefined value to use in a test script step. In this scenario, the value can be specified during execution. In the 6.0 release, the display of appending the specified value to the variable during execution was incorrect. The resolution was to ensure that a placeholder is set in the test script step for the value, which requires the execution variable to have a default value. This resolution caused the regression that the execution variable cannot be created without a predefined value.

Return to the top of the page


Return to the top of the page


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Feedback
Was this information helpful? Yes No 1 person rated this as helpful.