DNG : Some permission are unassigned in project area created from custom process template

RDNG has only one built-in "process template", and you cannot customize it, officially. You can read more about it in the below article.
https://jazz.net/library/article/1230
(Note that the article talks about how to customize it but it is not supported).

In a Lifecycle Project Template, the RDNG template being referenced is that "project template", as you have been aware of. So if you need a customized project template, you should customize an existing project, then create a project template out of it, and reference this new project template in the lifecycle project template.

I'm a bit confused of the meaning of "exported process template of this project area and imported it back to server". Did you mean the "process template" or the "project template"? Why did you need to "import it back"?

  Hi Donald,

I recently had a customer who also had this same question. In my investigation - I found enhancement request that describes this same scenario:

https://jazz.net/jazz03/web/projects/Requirements%20Management#action=com.ibm.team.workitem.viewWorkItem&id=111376

Based on the discussion in the RFE - it was determined that this is a current limitation of DNG as described in the following doc: https://jazz.net/library/article/1548#TOC_111376
 where we provide:

"If you attempt to share a process configuration between project areas, the sharing might partially function. However, the permissions for some Save Artifacts and Save Link actions do not work. The permissions are not inherited for any action related to a specific artifact type or link type (whether built-in or custom)."