How can I control location of base artifact when adding new requirements in a module?
![]() In DOORS NG 5.0.2, I created a module for a requirements document. Whenever I inserted a new artifact in the module, the base artifact ended up in a folder of supporting artifacts for that module. This was nice because when I browse artifacts I just see the module in the top-level folder and can open it from there, with all the base artifacts comprising that module nicely located in the Module's supporting artifact folder.
Since that time, we have migrated to DOORS NG 6.0.2 using ReqIF files (it was not an upgrade, it was a move to a new server with the upgraded DOORS instance).
Now when I create a new artifact in my requirements module, the base artifact shows up at the same level as the module itself (it does not get filed in the supporting artifact folder). This behavior is undesirable because it starts to clutter my view...I would like newly created artifacts in a module to go into the supporting artifact folder like they did in 5.0.2. Why is this behavior different? Is there a setting to make it work the way it did in 5.0.2?
Thanks,
Matt
|
Accepted answer
![]()
Benjamin Silverman (4.1k●6●10)
| answered Apr 19 '17, 5:15 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Hi Matt,
Matt Rosenthal selected this answer as the correct answer
|
One other answer
![]() There is a more universal setting under "Manage Component Properties" for all modules in a component. Under Manage Properties, select the Tab for 'Module Options', browse to the folder where you want the base artifacts to be created. Using this features helps keep the end-users working inside the modules instead of the base artifacts. Optionally set the base artifact folder to appear alphabetically last in the folder list. |
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.