Currently, requirements need to be linked to projects and/or products. It would be very helpful to establish requirements independent from specific projects and/or products and link them as needed to projects and/or products at a later stage. This would allow to "re-use" generic requirements.
Maybe,
someone could recommend an alternative method or workaround.
Thanks,
Georg
ALternative is already proposed : possibility to copy Requirements when copying project.
So you can define a template project with template requirements that will be copied when you copy the project.