It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,844

question asked: Jul 14 '09, 2:52 a.m.
question was seen: 6,172 times
last updated: Jul 14 '09, 2:52 a.m.

Related questions

RTC 2.0 Component access control question

0
Ming Xia (121●49●36) | asked Jul 14 '09, 2:52 a.m.
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 ?

2 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Jose Miguel Ordax Cassa (2.4k●4●126●100) | answered Jul 14 '09, 2:58 a.m.
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.
0
permanent link
Ming Xia (121●49●36) | answered Jul 24 '09, 4:28 a.m.
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!

Your answer

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