Artifact-specific Permission definitions can not be shared with another Project via Process Template if Projects are Config enabled

These are the steps to reproduce the problem on a single server with default Jazz/DNG templates:

• Create a new Project Area ptest1 from Template "Requirements Management application template"
• Enable Configuration Management for ptest1
• Initialize the ptest1 Component from "Traditional Requirements Template"
• Modify the Permissions in ptest1 Project Area for role Author:
• Revoke Permission for: Requirements Management Ressourfces/Save Artifact/Create an artifact/Create an artifact of a specific type/Create Release Collection artifact [ptest1 Initial Stream]
• Revoke Permission for: Requirements Management Ressourfces/Save Artifact/Modify an artifact/Modify an artifact of a specific type/Modify Release Collection artifact [ptest1 Initial Stream]
• Revoke Permission for: Requirements Management Ressourfces/Save Artifact/Delete an artifact/Delete an artifact of a specific type/Delete Release Collection artifact [ptest1 Initial Stream]
• Save Permission definition of ptest1

Imagine that ptest1 is our central place to define the data model and role permissions. For projects to use this central data model we create separate project areas usually on another server. But even on the same server we face issues when we intend to copy data model and role permissions to another project area ptest2:

• Export a new Process Template from ptest1
• Import Process Template created in previous step into server
• Create a new Project Area ptest2 from Template imported in previous step
• Enable Configuration Management for ptest2
• Initialize the ptest2 Component from "Traditional Requirements Template"
• Check Permissions of ptest2: Author is neither allowed to create, to modify, nor to delete any typed artifact (in ptest2 Initial Stream)

The data model of ptest1/ptest2 Initial Stream is identical. So is the role-permission defintion.

How can we share permission setting for a common data model without the need to manually adjust project area configuration for every Component/Stream?
 
In DNG with Configuration Management enabled permissions for Modify Artifact are not shared properly between a sharing project area A and a project area B that uses the process configuration from another project area A for this project area B
The permissions in the derived project area B are not identical to the permisions in A for "Save Artifact". The permissions in B are more restrictive.
This is a severe bug and represents a blocking point.
Also permission "Save Links" has this problem.
Request: Propagate all permissions from source to target project.

Steps to reproduce:
1. Create a Process Template from Templates_DivC_RM and download it.
2. From the appropriate Stream in Templates_DivC_RM create a Component Template and download it
3. Upload the Process Template to a BU server
4. Create a new Project Area from the uploaded Process Template
5. Enable the new Project Area for Configuration Management
6. Uploaded the Component Template
7. Apply the uploaded Component Template
=> Check the permissions. They are different:
Permissions in source Project Area: attachment 260
Permissions in new Project Area: attachment 261