It's all about the answers!

Ask a question

Changing the template for Non-GC project areas

Divya _ (254) | asked Feb 05, 11:20 a.m.
Hello Team,

Currently we are having many templates being used across our project areas and hence, planning to maintain a common template for both GC migrated and Non-GC project areas.

Could you please let us know if the OSLC Link/Attribute Mapping configuration would create any impact in the Non-GC project areas, if the default configurations are retained?

OSLC Link/Attribute Mapping

Thanks a lot in advance.

Accepted answer

permanent link
Ralph Schoon (63.1k33646) | answered Feb 07, 7:12 a.m.

  As far as I am aware, there is no simple way to migrate from one "Template" to another. Templates are used to initialize the project areas process. Once this is done, the process is what it is. You can modify the process, your changes do not have any relationship to any process template. 

If you use process sharing, you have to use the unconfigured process in the inheriting project areas. You can enhance the shared process and the inheriting project areas get the changes. However, if you switch to inherit a completely different process from another project area, that will not work.  

I can not answer your other question. I think the check box "Enable user selection...." was implemented for this reason. I can't remember what the exact situation was. Worst case you will have to maintain two project areas that share, or you will have to remove the final flag here and override the process in the inheriting project area. 

Divya _ selected this answer as the correct answer

Your answer

Register or to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.