Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Fine-grained Customization of Configuration Data - RTC 6.0.1 Support

 Hello,

Does RTC 6.0.1 supports Fine-grained Customization of Configuration Data ?

We have some core processes for problem management. We have taken Scrum template as a base and customised scrum processes to meet our needs. The customised template is a base process template for multiple departments within our organisation. But each department has a flexibility of adding attributes and wotkitem types as per their need. When we configure do shared project one as master and others as slave, if slave customises configuration data, the link with master is broken. It no more inherits configuration from master.

If Fine-grained Customization of Configuration Data is not supported, what is the best practice to do it in RTC 6.0.1 ?

Thanks.

0 votes


Accepted answer

Permanent link
There are a set of specific customizations you can do without breaking the master/child relationship.
Note that they are done via editing the process XML (no GUI for it yet). 
This is described in the online documentation:
https://www.ibm.com/support/knowledgecenter/SSCP65_6.0.2/com.ibm.jazz.platform.doc/topics/c_sharing_project_area_process.html

That page will point you to the following wiki page for details:
https://jazz.net/wiki/bin/view/Main/ConfigurationDataDeltaUserDoc
IBM Rational Product User selected this answer as the correct answer

0 votes

Comments

 Thanks Geoffrey.


We have three server (Dev, QA, Prod). What will be your recommendation on migrating/importing process template changes from Dev to QA to Prod ? Do you recommend the same  approach of updating XML in master project ?

Thanks.


I wouldn't recommend updating the XML in the master project, only in the slave projects (and I only recommend updating the XML in the slave projects if you are adding/removing delta XML declarations in the slaves).   One reasonable approach for migrating process changes is to create a process template from the current master, create a new project area in Dev from that template, and then make your process modifications in that new Dev master project area.   When you are happy with the new process, close down that new master project area for changes, and notify your project admins to share from the new master project area (they can share back to the original master project area if things don't look right).   Note that I'm not bothering with a separate QA project area, but rather doing QA against the new dev master project area.

1 vote

 Thanks Geoffery.


Can you share any post which explains impact of changing your master process template reference on slave project data? 


Your answer

Register or log in 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.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 7,495
× 6,121
× 457

Question asked: Jun 24 '16, 10:59 a.m.

Question was seen: 2,988 times

Last updated: Oct 01 '16, 12:30 a.m.

Confirmation Cancel Confirm