Recovering module artifacts cause new ReqIf identifier for the recovered artifacts

Situation 

(Individual CS delivered for every step): 

- STR Document import by ReqIf provided by customer
- STR artifact is removed from STR Document (not deleted)
- STR artifact is added again (recovered)

Result:

The recovered artifact gets a new ReqIf identifier.
As consequence, it's not recognised as the original artifact on customer side. I.e. an exchange for this artifact is no more possible. The customer has to duplicate the artifact in his system and export it again.
(Note: In our case the customer denied to do so, since the artifact was a child of a master (template) document. Hence he would also have to replace the master (template) requirement.)

Additional investigations made on Test4 with iFix19:

Re-import of the ReqIf does also not recover artifact. It will be ignored

Deletion of the artifact also has no effect

If artifact is added again to the module it is exported, but with a different reqif identifier

No possibility is given to change the ReqIf identifier manually, also not with Administrator rights or Data Model Manager rights.

Requests:

Provide the possibility to recover removed artifacts with original ReqIf identifier or to manipulate ReqIf identifiers.

Following workaround is possible but not a real solution:

Create a stream based on the baseline before the artifact was removed

It's difficult to identify the correct CS, where this happened

Only one stream of a component can be selected by GC. What shall happen with all the CS in between? Maybe there was a lot of development in between. But CS can not be accepted to new stream, since the artifact could be removed again.

The concept to do everything on Generic contradicts with this new stream