Best practice for organizing and moving large number of requirements into a DNG module
![]() I have a need to organize my requirements into sets. I then need to copy the sets into modules. I tried using collections as the container, but collections cannot be added to a module. I then created a new artifact to use to hold the requirements and then added the new artifact to my modules. That work properly, but it will not print the contents of the requirements, only the title of the requirement. I am probably over thinking this. Is there a best practice for organizing requirements and using a set of requirements in a module? I also know I can use tags, but tagging a bunch (100s) or requirements just to add them to a module is cumbersome. Thanks! |
One answer
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.