QUESTION: Limiting Visibility of Work Items

Hi,

seee answer in http://jazz.net/forums/viewtopic.php?t=11191

Ralph

Hello Everyone,

If I have two teams, A and B, defined under my project area, how can I create a work item that is visible to team A, but not team B?

Thank you in advance!

Andrew

In 2.*, all work items in a project area have the same visibility (as
specified by access control on that project area). In 3.0, you will be
able to specify read access separately on each work item.

Cheers,
Geoff

On 6/17/2010 9:36 AM, spriteburn wrote:

Hello Everyone,

If I have two teams, A and B, defined under my project area, how can I
create a work item that is visible to team A, but not team B?

Thank you in advance!

Andrew

Hi,

I have been testing this functionality in RTC 3.0M6 and this new
functionality allows to change the Project Area, but the change is not
related with any of the teams/groups of the first project Area.

These are the steps I have followed: I created the work item in
Project_Area_A that has two teams (TeamA and TeamB). There is also
another Project_Area_B. I use "Restricted Access" menu for the work item
created in Project_Area_A, but instead of showing TeamA and TeamB I have
only two options to select: "Public" and "ProjectArea_B". Does this mean
that this functionality allows to change read permissions between
different project areas but not inside the same project area ?

Probably I am doing something wrong...

Thanks,

Ana

On 17/06/2010 17:59, Geoffrey Clemm wrote:

In 2.*, all work items in a project area have the same visibility (as
specified by access control on that project area). In 3.0, you will be
able to specify read access separately on each work item.

Cheers,
Geoff

On 6/17/2010 9:36 AM, spriteburn wrote:
Hello Everyone,

If I have two teams, A and B, defined under my project area, how can I
create a work item that is visible to team A, but not team B?

Thank you in advance!

Andrew

You are correct that you cannot currently use a Team membership list as
the basis for read access control. The ability to do so has been
requested in work item 102270 ("Allow team member list to be used for
specifying read access control"). That work item is currently marked as
"won't fix", but if you are interested in this functionality, please go
ahead and add a comment to that work item (maybe we can at least get it
moved from "won't fix" to "backlog" (:-).

Cheers,
Geoff

On 6/21/2010 3:12 AM, Ana Lopez wrote:

Hi,

I have been testing this functionality in RTC 3.0M6 and this new
functionality allows to change the Project Area, but the change is not
related with any of the teams/groups of the first project Area.

These are the steps I have followed: I created the work item in
Project_Area_A that has two teams (TeamA and TeamB). There is also
another Project_Area_B. I use "Restricted Access" menu for the work item
created in Project_Area_A, but instead of showing TeamA and TeamB I have
only two options to select: "Public" and "ProjectArea_B". Does this mean
that this functionality allows to change read permissions between
different project areas but not inside the same project area ?

Probably I am doing something wrong...

Thanks,

Ana

On 17/06/2010 17:59, Geoffrey Clemm wrote:
In 2.*, all work items in a project area have the same visibility (as
specified by access control on that project area). In 3.0, you will be
able to specify read access separately on each work item.

Cheers,
Geoff

On 6/17/2010 9:36 AM, spriteburn wrote:
Hello Everyone,

If I have two teams, A and B, defined under my project area, how can I
create a work item that is visible to team A, but not team B?

Thank you in advance!

Andrew

You are correct that you cannot currently use a Team membership list as
the basis for read access control. The ability to do so has been
requested in work item 102270 ("Allow team member list to be used for
specifying read access control"). That work item is currently marked as
"won't fix", but if you are interested in this functionality, please go
ahead and add a comment to that work item (maybe we can at least get it
moved from "won't fix" to "backlog" (:-).

Cheers,
Geoff

On 6/21/2010 3:12 AM, Ana Lopez wrote:
Hi,

I have been testing this functionality in RTC 3.0M6 and this new
functionality allows to change the Project Area, but the change is not
related with any of the teams/groups of the first project Area.

These are the steps I have followed: I created the work item in
Project_Area_A that has two teams (TeamA and TeamB). There is also
another Project_Area_B. I use "Restricted Access" menu for the work item
created in Project_Area_A, but instead of showing TeamA and TeamB I have
only two options to select: "Public" and "ProjectArea_B". Does this mean
that this functionality allows to change read permissions between
different project areas but not inside the same project area ?

We have discussed the option to introduce explicit user groups for this
purpose, instead of relying on project or team area membership. This
request is tracked in

https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/102614

and I have created

https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/118600

to track the request explicitly in context of the read permissions.

--
Regards,
Patrick
Jazz Work Item Team

I don't believe adding the notion of a group addresses this use case.
In particular, the member list of a team area needs to specify the roles
of each of those members, so a group isn't sufficient to specify the
member list of a team area. So without the ability to have a team area
member list effectively form a "group" for the purposes of read-access,
you'd still be stuck with defining that list in two different places ...
one in the team area member list, and the other in the "group" member list.

I've also posted this response in work item 102270 ... in case folks
would prefer to take this thread off the forum and continue the
discussion in the work item.

Cheers,
Geoff

On 6/21/2010 10:21 AM, Patrick Streule wrote:

You are correct that you cannot currently use a Team membership list as
the basis for read access control. The ability to do so has been
requested in work item 102270 ("Allow team member list to be used for
specifying read access control"). That work item is currently marked as
"won't fix", but if you are interested in this functionality, please go
ahead and add a comment to that work item (maybe we can at least get it
moved from "won't fix" to "backlog" (:-).

Cheers,
Geoff

On 6/21/2010 3:12 AM, Ana Lopez wrote:
Hi,

I have been testing this functionality in RTC 3.0M6 and this new
functionality allows to change the Project Area, but the change is not
related with any of the teams/groups of the first project Area.

These are the steps I have followed: I created the work item in
Project_Area_A that has two teams (TeamA and TeamB). There is also
another Project_Area_B. I use "Restricted Access" menu for the work item
created in Project_Area_A, but instead of showing TeamA and TeamB I have
only two options to select: "Public" and "ProjectArea_B". Does this mean
that this functionality allows to change read permissions between
different project areas but not inside the same project area ?

We have discussed the option to introduce explicit user groups for this
purpose, instead of relying on project or team area membership. This
request is tracked in

https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/102614


and I have created

https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/118600


to track the request explicitly in context of the read permissions.