move content from one project area to another
Is it possible to move content / artifacts from one project area to another?
We have a single project area where we do all our development. But in the last couple of years, we've embraced agile and have started to work using agile.
The original project area was setup using traditional project management templates. We don't want to change this because work on our main product still happens in a waterfall manner. However, we want to move the content from our second development into a new "agile" project area.
|
One answer
Geoffrey Clemm (30.1k●3●30●35)
| answered Sep 03 '21, 1:51 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER It depends on what kind of content/artifacts you want to move.
For most types of ELM artifacts, the answer is "no".
An exception would be EWM work items, which can be moved to another project area on the same server.
Similarly, EWM versioned files don't really "belong" to a project area (they "belong" to a component), so you can "move" an ELM component to a different project area on the same server by just modifying the Project Area property of that component.
Comments For requirement artifacts, it is possible to export and import using ReqIF packages or project templates. You may need to touch up links afterwards, and you don't bring version history with you.
Similar story for test artifacts, I believe.
As I recall, the IBM Expert Labs services team have some utilities that help to "move" requirements and test artifacts (without all their history).
|
Your answer
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.