Welcome to the Jazz Community Forum
Restricting access to source but not work items.
2 answers
Yes, that is what I would recommend. And by "source in a different
project area", that means to have the components and streams for that
source code to be owned by a different project area.
Cheers,
Geoff
On 1/28/2011 8:38 AM, katsharp wrote:
project area", that means to have the components and streams for that
source code to be owned by a different project area.
Cheers,
Geoff
On 1/28/2011 8:38 AM, katsharp wrote:
Hi,
We've been trying to figure out how to allow one group of users access
to work items in a given project, but no access to source code.
We think we can do this by having the source and work items in
separate project areas, is this the recommended approach?
Ok, thanks
Yes, that is what I would recommend. And by "source in a different
project area", that means to have the components and streams for that
source code to be owned by a different project area.
Cheers,
Geoff
On 1/28/2011 8:38 AM, katsharp wrote:
Hi,
We've been trying to figure out how to allow one group of users access
to work items in a given project, but no access to source code.
We think we can do this by having the source and work items in
separate project areas, is this the recommended approach?