Copying artifacts between projects
You can copy artifacts between projects in the Requirements Management (RM) application.
Before you begin
- You are logged in as a user with JazzAdmins or JazzProjectAdmins repository permissions. You are assigned the Administrator role.
- Both projects have the same setting for configuration management: either both are enabled or both are disabled.
- If you use global configurations, ensure that you are using a global configuration that has contributions from both projects.
- The target project contains the same artifact types, artifact attributes, and attribute data
types as the artifacts in the source project.Important: To copy artifacts, the target project must contain the same artifact types as the source artifacts that are being copied, including URIs or artifact names. Otherwise, no artifacts are copied. If the target project does not contain the same artifact attributes or attribute data types, the source artifacts are copied, but the attribute values are not.Note: When copying and pasting modules or collections across components or projects, the shared and private views of the module or collection are copied. If the target component or project contains views that are shared across all modules or collections of the same type or shared across all modules or collections. And have the same name as the reused views in the copied module or collection, the copied views are not resolved. Instead, multiple views with the same name exist after the paste operation is run and must be resolved manually.
In projects that are enabled for configuration management, confirm whether you want to copy artifacts between components or clone them. To help you decide, see Cloning artifacts between components.
About this task
You can copy most artifacts between projects, including collections, modules, embedded artifacts,
and diagrams. However, the copy function does not support copying the following items:
- Graphical artifacts that require a browser plug-in, such as sketches, storyboards, screen flows, and business and use case diagrams
- Tags
- Comments
Note: Copying and pasting of artifacts between streams in the same component is not allowed. A
more appropriate way to move data from one stream to another is to deliver the change set(s) that
contain that data. This ensures you get the same concept in both places and that the version history
is correct. At that point, if you want to copy the artifact somewhere else within the stream you may
do so. Alternatively, you can also copy or paste within your current stream and then deliver the
change set.