RRC Team Ownership for Folder - Limitations
In RRC one can assign team ownership to Folders .
In ideal scenario, once ownership is assigned only members team area which owns the folder can create artifacts in that folder. But under following (most common) scenarios, team ownership concept will break . It will also have limitation mentioned below.
let know your thoughts on overcoming these limitations
1. Team ownership does not prevent users from other team areas in moving away artifacts
2. If user is member of team area and create artifacts, they won't be able to initiate RRC Review Process
- RRC review process can be initiated only users who are part of Project Area
3. If you add a user to Project Area, in order to allow users to create/initate RRC Review, Then the user will get access all folders owned by different team areas
" " Team areas are hierarchal. Users who are members of the parent project or team area are effectively members of the child team areas. Consequently, if users need to have permissions set in multiple team areas, you can add them to a parent team area. "
4. Users are restricted from linking artifact which are in different folders owned by different team area.
Only way to grant this is set permission at project area level - Set permission to Every One, not any custom roles
5. Team area ownership , does not restrict artifact visibility
6. Team ownership at folder level alone won't provide privilege on artifact, ensure change ownership of artifact in the folder which setting up team ownership
Looking for your recommendations,
Best Regards
|
One answer
There are a lot of questions here, but maybe one thing that would help is that while you can add new members to the project area, you can restrict their access if you remove certain permissions from the root folder. This will prevent the type of inheritance that you referred to in #3.
I would also mention that a few defects have been discovered and fixed in more recent (and upcoming) versions of RRC that may address some of your other points. |
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.