does it make sense to import two different hierarchy files with same requirement IDs?
in Polarion it duplicated all requirements instead of updating the existing with same ID.
any idea how can we solve this gap ?
This is one of those frustrating situations where the tool is not as powerful as the ReqIF standard: While ReqIF supports references (reusing the same requirement in different Specs), Polarion does not.
The “best” solution is to simply not use references. Incorrectly handled references can create lots of problem (e.g. unintended side-effects from changing a requirement).
If you need references, then you probably need tool-(Polarion)-specific scripting. You need to map the references to Polarion’s reuse mechanism. This is possible, but potentially error-prone and brittle.