Skip to main content
J
JC_52474974-Participant
4-Participant
November 17, 2025
已解决

Codebeamer Requirements library

  • November 17, 2025
  • 1回复
  • 399查看

Hi all,
I would like to use a project as a library (see Requirements Library) and re-use or copy several trackers while maintaining their links or downstream references. It does not seem to be possible; for example, I have functional requirements and safety requirements that are interconnected. However, once I drag and drop using the library option, I lose the link between the two. Is CB able to do this, and if so, what are the conditions or procedure? The only connection that is kept is for the test cases. Why is that?

最佳答案由 GeoffreyClemm

To upgrade from v21.09 to 3.x, you would follow the upgrade procedure in the 3.x release notes.   

For example, to upgrade to 3.1, see: https://support.ptc.com/help/codebeamer/r3.1/en/#page/codebeamer/release_notes/whats_new_in_codebeamer_3_1_0_0.html

Note that creating a ZIP file and importing it is not part of that procedure.

 

1回复

G
GeoffreyClemm13-Aquamarine
13-Aquamarine
November 17, 2025

If you want to maintain the links/references between reused items, you will want to use working-sets (or if you have upgraded to 3.1, streams) for re-use, rather than the library mechanism.

J
JC_52474974-Participant作者
4-Participant
November 19, 2025

I will try in the future but for now I have exported the project as a Zip and reimported it again. 

My company is working with license version 21.09 and therefore my question is that Zip export the way to use to migrate to the version 3.x?

G
GeoffreyClemm13-Aquamarine
13-Aquamarine
November 26, 2025

When you say "migrate to version 3.x", do you mean migrate from using the library mechanism for re-use (where each "branch" is a separate Codebeamer project) to using the stream mechanism for re-use (where each "branch" is a separate stream)"?  (Just migrating to 3.x without changing the way you do reuse does not require any export/import).  Also note that you can migrate from using the library mechanism to using the working-set mechanism in 2.x and 3.0, but commonly one does not do this migration until 3.1 is installed, because reuse is much more efficient and effective with streams than it is with just working-sets.

The simplest approach to adopting the stream based re-use mechanism is not to migrate anything, but rather to keep using your current reuse approach (different projects) for existing branches, but to use streams for any new branches.

条款和条件Cookie设置Accessibility statement