RTC 2.0 Component access control question
RTC 2.0 has new feature to control the access between project area. If the user want to control the access for components, he can put the components into a project area which open the access control.
However, in some scenario, user wants the access control within a project area for different project team. In other words, project team A cannot update the components owned by project team B, although project team A and B belong to one project.
I tried, but RTC 2.0 doesn't support this scenario. Could we have enhancement on this?
Should I submit work item ?
However, in some scenario, user wants the access control within a project area for different project team. In other words, project team A cannot update the components owned by project team B, although project team A and B belong to one project.
I tried, but RTC 2.0 doesn't support this scenario. Could we have enhancement on this?
Should I submit work item ?
2 answers
XiaMing wrote:
Theoretically such scenario is supported by RTC 2.0.
Check "Restricting deliveries to components" topic in this URL:
https://jazz.net/downloads/rational-team-concert/releases/2.0?p=news#scm
Hope this helps,
Chemi.
RTC 2.0 has new feature to control the access between project area. If
the user want to control the access for components, he can put the
components into a project area which open the access control.
However, in some scenario, user wants the access control within a
project area for different project team. In other words, project team
A cannot update the components owned by project team B, although
project team A and B belong to one project.
I tried, but RTC 2.0 doesn't support this scenario. Could we have
enhancement on this?
Should I submit work item ?
Theoretically such scenario is supported by RTC 2.0.
Check "Restricting deliveries to components" topic in this URL:
https://jazz.net/downloads/rational-team-concert/releases/2.0?p=news#scm
Hope this helps,
Chemi.
XiaMing wrote:
RTC 2.0 has new feature to control the access between project area. If
the user want to control the access for components, he can put the
components into a project area which open the access control.
However, in some scenario, user wants the access control within a
project area for different project team. In other words, project team
A cannot update the components owned by project team B, although
project team A and B belong to one project.
I tried, but RTC 2.0 doesn't support this scenario. Could we have
enhancement on this?
Should I submit work item ?
Theoretically such scenario is supported by RTC 2.0.
Check "Restricting deliveries to components" topic in this URL:
https://jazz.net/downloads/rational-team-concert/releases/2.0?p=news#scm
Hope this helps,
Chemi.
Chemi,
Thank you very much. Following that guide, I have deployed the scenario successfully!