Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

Why, when using the Requirement Grid are some requirements reported as belonging to the wrong project?

Why, when using the Requirement Grid are some requirements reported as belonging to the wrong project?

Problem:

Why, when using the Requirement Grid are some requirements reported as belonging to the wrong project?

Resolution:


  • Product Name: CaliberRM
  • Product Version: All
  • Product Component:
  • Platform/OS Version: All

Sometimes it is necessary to move a set of requirements from one project to another. There have been instances with databases migrated from older versions to 2008, where using the Requirement Grid to report on requirements, that had previously been moved between projects, reported the requirements as belonging to the project that they were moved from. This can be resolved by using the CRMDiag tool. Please contact Caliber Support for the correct version of the CRMDiag tool and the command required to resolve this problem.

Old KB# 30142

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Version history
Revision #:
1 of 1
Last update:
‎2013-02-15 20:43
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.