I do not believe there is a way ootb to set this type of behavior, aside from restricting modification to attributes by roles, which is not the dynamic type of ownership control you are looking for.

It would be a custom operational behavior control or possibly a attribute customization through conditions.

I believe the intent of allowing anyone in the permitted role to modify WIs is to provide a high level of collaboration while still maintaining a detailed field level audit record on the WI's history.  You will always know who, when and what was changed for an attribute including the prior value.

I would look to a custom operational behavior for this type of restriction.

-Chris

RTC is a tool for collaboration and not for disclosure or restricting people. The assumption is the teams are self managed and responsible.

However, some projects don't necessary agree to this kind of openness and collaboration. I don't have time to look if there is that kind of OOTB functionality, but I doubt it. The other thought is, that you don't want to restrict changing of the whole set of attributes anyway. You would still want to allow comments for example.

So you can implement this kind of restriction by creating an Advisor - see  https://jazz.net/library/article/1000 for a general introduction on extending RTC operational behavior and http://rsjazz.wordpress.com/2012/11/01/restrict-delivery-of-changesets-to-workitem-types-advisordelivery-of-changesets-associated-to-wrong-work-item-types-advisor/ for an advisor example with source code. There are also some advisors in the Wiki: https://jazz.net/wiki/bin/view/Main/RtcSdk30 .