RaQuest and generated use case requirements

[Wigo4it]

I am evaluating RaQuest for use in a large program together with EA. When I generate use case requirements from use cases, the generated use case requirements end up in the root requirements package. I do not want this. That way, I would get a huge list of UC requirements under the root requirements package. Instead, I would like these generated requirements to appear in a separate package (per project or in one package defined for the entire program) so that I can easily hide them in EA.

If I move the generated requirements to another package, each UC requirement is generated anew under the root package when I run the tool, so obviously that is not the way to go.

Is there any way to achieve this?

[umesan]

"Generate Requirements from Use Cases" command of current RaQuest only corresponds with root package.
So, when UseCases Package is changed in the "Generate Requirements from Use Cases" dialog, a new element is created.

At the same time, RaQuest corresponds with package structure as well, so would it be an alternative to create a package in the target UseCases packages?

In other words, when UseCases in the package "View.UseCases.Package1" corresponds with RaQuest, select a package of "View.UseCases", but not "View.UseCases.Package1", in the "Generate Requirements from UseCases" dialog.
Would it meet your request?

[Wigo4it]

Thank you, your second suggestion will meet our needs.