It's all about the answers!

Ask a question

Restricting Access to Assigned Work Items


Yohannes Tadesse (2672) | asked Sep 15 '08, 5:24 p.m.
JAZZ DEVELOPER
Is it possible to restrict team members from seeing eachother's assigned work items? For example, if I'm a manager, I may not want developer X to know that I've assigned developer Y half the work.

8 answers



permanent link
David Olsen (5237) | answered Sep 15 '08, 7:53 p.m.
JAZZ DEVELOPER
ytadesse wrote:
Is it possible to restrict team members from seeing each other's
assigned work items? For example, if I'm a manager, I may not want
developer X to know that I've assigned developer Y half the work.

No, it's not possible. There is no way to restrict read access to work
items in a Jazz repository.

Many people have requested (quite reasonably) the ability to prevent
members of one project from seeing the work items in a different
project. But yours is the first request I have seen to restrict read
access for people on the same team. To me that doesn't make sense.

One of the strengths of Jazz is the ease with which the entire team can
see what the entire team is doing. That visibility fosters cooperation
and collaboration between team members and helps identify conflicts
sooner rather than later. If I am developer X and I need to work on the
same team as developer Y, I want to know what developer Y is working on.
Not being allowed to know that would cause conflicts and inefficiencies.

permanent link
James D'Anjou (2011411) | answered Sep 15 '08, 11:21 p.m.
No. I suppose there is a good reason for this but on the surface your
example would appear to be contrary to the notion of transparent
development and inhibits team collaboration.

Jim D'Anjou
Jazz/RTC Jumpstart

ytadesse wrote:
Is it possible to restrict team members from seeing eachother's
assigned work items? For example, if I'm a manager, I may not want
developer X to know that I've assigned developer Y half the work.

permanent link
Peter Wrampe (411514) | answered Sep 16 '08, 7:29 a.m.
There are reasons why one team would not want outsiders or outside teams to have access to their project, YET, still work as a team.

One example could be that I have 10 consultants working within RTC on a project, and our team (team of 50) is working on a new confidential project. Above us, management wants to run reports and have visibility across and containing it all.

permanent link
Geoffrey Clemm (29.5k23035) | answered Sep 16 '08, 8:15 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Yes, providing read access control is very important, and a high
priority item for RTC 2.0. The workaround for RTC 1.0 is to put the
confidential projects into a separate repository.

Cheers,
Geoff

pawrampe wrote:
There are reasons why one team would not want outsiders or outside
teams to have access to their project, YET, still work as a team.

One example could be that I have 10 consultants working within RTC on
a project, and our team (team of 50) is working on a new confidential
project. Above us, management wants to run reports and have
visibility across and containing it all.

permanent link
Dong Lieu (5632) | answered Jul 27 '09, 1:40 p.m.
What about the notion of limiting write access. As in CQ (RATLC) for example only the work item submitter and admins can modify work items, that does not seem to be restricted in RTC 2.0. It could be quite dangerous...any plans for this in the future?
Thanks,

permanent link
Geoffrey Clemm (29.5k23035) | answered Jul 27 '09, 9:44 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Write access to work items can be controlled in quite fine-grained ways
by using Jazz process. This has been the case since the first release
of RTC-1.0. See the permissions section of the project area's process
definition.

Cheers,
Geoff

dlieu wrote:
What about the notion of limiting write access. As in CQ (RATLC) for
example only the work item submitter and admins can modify work
items, that does not seem to be restricted in RTC 2.0. It could be
quite dangerous...any plans for this in the future?
Thanks,

permanent link
Dong Lieu (5632) | answered Jul 29 '09, 9:24 a.m.
Hi Geoff,
I see all the permission attributes for my team (contributor, managers, etc..). I would like to allow only the submitter of the work item to modify it along with the admins. If unselecting "add comment" from the Modify work item permissions for contributors does that now mean anyone belonging to contributors can not add comments or only those that did not create the original work item...

Write access to work items can be controlled in quite fine-grained ways
by using Jazz process. This has been the case since the first release
of RTC-1.0. See the permissions section of the project area's process
definition.

Cheers,
Geoff


permanent link
Geoffrey Clemm (29.5k23035) | answered Jul 29 '09, 11:36 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Currently, you cannot give special permissions to the "creator" of an
object, but I agree that you should be able to. I've submitted work
item 88779 for this enhancement.

Cheers,
Geof

dlieu wrote:
Hi Geoff,
I see all the permission attributes for my team (contributor,
managers, etc..). I would like to allow only the submitter of the
work item to modify it along with the admins. If unselecting
"add comment" from the Modify work item permissions for
contributors does that now mean anyone belonging to contributors can
not add comments or only those that did not create the original work
item...

gmclemmwrote:
Write access to work items can be controlled in quite fine-grained
ways
by using Jazz process. This has been the case since the first
release
of RTC-1.0. See the permissions section of the project area's
process
definition.

Cheers,
Geoff


Your answer


Register or to post your answer.