How to change the type of a new issue in RTC-SCM Code review component of 6.0.1?

In RTC 6.0.1 the issue types in Code Review are a fixed set. There was an enhancement request (369933), but we  ended up removing 'issue types' all together in 6.0.2. In RTC 6.0.5 we added the ability to allow the project administrator to define a set of tags that can be set on a code review issue. We expect this to be general purpose enough for customers to meet their workflow/process needs. For example, a set of tags could be created to represent the 'type' of the issue (ex: 'defect', 'best practice', 'question', 'invalid'), or to represent issue states such as 'verified', etc.


For additional information about RTC Code Review, please see:
Article: Rational Team Concert Code Review
Video: Introduction to Code Review (Part 1)
Video: Configuring Code Review (Part 2)
Video: Performing a Code Review (Part 3)
Knowledge Center: Working With the Code Review Tool

I tried it just now, but it doesn't seem configurable. I will follow up on this internally to see if I missed how to configure it, or if I didn't can we make an enhancement out of it.

Absolutely.. If you use process sharing, then the child should get everything the parent has, including updates

EXCEPT if the child was allowed to make changes to the enum on its own.  If it is allowed (you didn't mark this 'final' in the parent), then IF the child changes the enum, it get s COPY of the list at that moment and is forever disconnected from future parent changes for (ALL) ENUMs.

you can test this pretty easily..
set final in the parent (shared) process config, and all children should see ONLY the parents config.
(ie, it will ignore completely any child configuration).
unset final and the child config will appear again.

this area is one of the sections that has child configurability allowed,  see
https://jazz.net/wiki/bin/view/Main/ConfigurationDataDeltaUserDoc