Why a developer at project area level can't see team comp?

Hi Jirong,

please read https://jazz.net/library/article/291 carefully.

I think the problem is, that the user has no access to the components.
The reason is, they are private to the team. That means only team members can access them. Adding build to the project provides general access to data in the project and in teams with no read restrictions such as read access only for team members. You would have to add the build user to the team to allow access to the data in the private component, or you change the scope of users allowed to read the data.

Hi Ralph

What I don't understand is my current production is also setup like that.

Please see this screenshot. "rtcbuilduser" is added at the project area level, never inside any other sub teams. As you notice, the stream and components is owned by "MDM Foundation Integration" team, but "rtcbuilduser" is not part of this team. It's just a "JazzUsers", not "JazzAdmins". What else can make this user be able to see everything?

As usually, the guys originally set it up left with no document.

https://lh4.googleusercontent.com/-zIu4i2xfBG0/T6KQdTO1x7I/AAAAAAAAFlM/GEzXEI_oH4g/s1101/rtcbuilduser.png

What do you mean by "change the scope of users allowed to read the data"?

Thanks
Jirong

The following comes into mind.

1st: Check if the other build user has a build system license.
2nd: Open the stream(s) and check if the visibility is set to project level.
3rd: Right click on the components and check the owner and also if visibility is restricted to the team (checkbox bottom left).
4th: A user that is not in a team has role everyone(default) in that team. are there any differences in the permissions, especially related to SCM?

Also log into eclipse as the build user and try creating repo workspaces and look at the errors that come up to get a clue what it could be.

I am looking at a beta so your UI might have differences to what you see or lacking some options.

I am comparing my production env and my test env in my VM. The above setup works in prod but not in my test.

1st: Check if the other build user has a build system license.

Yes. I made them both only have the build license.

2nd: Open the stream(s) and check if the visibility is set to project level.

No, as you can see from my first screenshot, integration stream is owned by the integration team and each development stream owned by sub development team. Both environments are not setup to the project level.

3rd: Right click on the components and check the owner and also if visibility is restricted to the team (checkbox bottom left).

I can't follow your instruction, from where to right click? And there is only change owner or change access control, no check owner. I try to right click a component from Source Control -> Components in both env, but got this message.

https://lh5.googleusercontent.com/-2VPESj2WAh0/T6LAUww3EWI/AAAAAAAAFmM/TytSamsfgFE/w1160-h378-n-k/comp%2Bowner.png

Then I notice the difference. In my test env (right), the component shows the owner in (), but nothing in my prod env.

The component is usually owned by sub team as you can see from my screenshot.

4th: A user that is not in a team has role everyone(default) in that team. are there any differences in the permissions, especially related to SCM?

The default user has no access to Source Control at team config or Source Data at project level at all.

Also log into eclipse as the build user and try creating repo workspaces and look at the errors that come up to get a clue what it could be.

As I said, my production env "rtcbuilduser" can see anything with no issue. But in my test env, this "build" user can't see anything in the stream. No error in creating a workspace to the stream, but of course, no components is showing. I just don't understand what's the different between my production and my own test environment in my VM. I try to setup in the same way.

I am looking at a beta so your UI might have differences to what you see or lacking some options.

Mine is 3.0.1

Finally I figured out.

The production is with RTC 3.0 and my test environment is RTC 3.0.1, because I don't see that Visibility option in UI. Once I try the production setup in a 3.0 test env, it works.

So now comes the question: why this change? To achieve the same result, I have to add this build user to every team!

Thanks
Jirong

No,

you can change the visibility of the components and stream to project level.

Visibility is important for projects especially in bigger companies. For instance to avoid intellectual property issues with open source code you want to restrict visibility to those who need to know. Or you work with external companies and want to avoid that the external users can see all code. Or you have high confidential code that only a few people are supposed to see.

After I talk to the team lead, here is the requirement (RTC 3.0):

1. We have three sub teams working on e.g. three components. These teams are used more in Scrum planning, rather than SCM.
2. Everyone in the project can R/W all components.
3. We have one development stream.

Here's what I've tested:

1. Three teams with their developers in the team, they are not as members of the project.
2. Streams and components all owned by the project.

The problem is: developers can check-in but can't deliver, because they are not member of the project. No permission on: modify/stream/deliver/changesets.

What shall I do to make this setup work?

Thanks
Jirong