Restrict Access to work items

In the 3.0.1 GA release, you can restrict work items at the team level
using the Eclipse UI. I believe the same is true for 3.0.1 RC2, but am
not sure about that.

Cheers,
Geoff

On 6/29/2011 7:08 AM, zvalsan wrote:

Hello,

I have currently RTC v3.0.1 RC2 and a PA with several teams and tried
to restrict the visibility access to the work items at the team
level.
From Web UI that works fine but when trying from Eclipse client, right
click on the new task/Restricted Access
the selected groups are actually only the Projects Areas. According
to the article https://jazz.net/library/article/554/ in
ver 3.0 the implementation of the Work Item Access Restriction
feature is based on Project-level membership. And so seems to work in
3.0.1RC2

Therefore my question is if this feature work item read
permission at team area level works from Eclipse too
in 3.0.1 as such or is any customization required in advance as in
3.0.1RC2 is not working.
I can't currently upgrade the server neither the client to the release
3.0.1 in order to test myself this feature.

Thank you,
Zica



I'm wondering if in the latest release this option

Hi Geoff,

thank you for the replay. I have managed to get 3.0.1 GA installed and indeed, I saw one can restrict the read access at teh team level in Eclipse client from Work Item Categories Tab.

Nevertheless, I don't mange to make sense of the feature Restricted Access whenever opening a new WI.

Here the scenario:

There are 2 PAs with different teams.
I open a WI from PA1, right click on it, choose Restricted Access. From there I have possibility to choose either PA1 or PA2.
Supposing I want to restrict the access to the PA2 and its corresponding teams. So, I choose PA2.
I expect the attribute Files Against to be pre-filed with the teams in the PA2
but they are not. Instead, all teams belonging to the PA1 where the WI is opened are listed.
What's the meaning of this? Do we want to let team members of a PA2 to see the WI in PA1?
If not, do we want to open a WI in another PA than that where I'm currently working? If so, then I should be able to see the teams in PA2 and not in PA1.

Thank you,
Zica

Note that there are two kinds of restricted access for work items.
The first, defined at the work item category level, affects any work
item that is assigned to that category.
The second, defined at the individual work item level, affects just the
specified work item.

When you right-clicked on a WI, you are dealing with the second kind of
restricted access (i.e. just affecting the individual work item).

So one interesting question is what happens when both kinds of
restricted access are activated for a particular work item (i.e. by
assigning its category to be a restricted access category, and by
restricting access on the individual work item). The logical
possibilities include:
- the individual restricted access overrides the category level
restricted access
- both restrictions apply (i.e. you must satisfy the restrictions at
both the category level and the individual work item level).

I'm guessing that the former is the case (i.e. that the individual
restricted access overrides the category level), but if we don't get a
post soon from someone who knows the answer, when I get a chance, I'll
experiment with this, and report back.

Cheers,
Geoff

On 7/4/2011 9:38 AM, zvalsan wrote:

Hi Geoff,

thank you for the replay. I have managed to get 3.0.1 GA installed and
indeed, I saw one can restrict the read access at teh team level in
Eclipse client from Work Item Categories Tab.

Nevertheless, I don't mange to make sense of the feature Restricted
Access whenever opening a new WI.

Here the scenario:

There are 2 PAs with different teams.
I open a WI from PA1, right click on it, choose Restricted Access.
From there I have possibility to choose either PA1 or PA2.
Supposing I want to restrict the access to the PA2 and its
corresponding teams. So, I choose PA2.
I expect the attribute Files Against to be pre-filed with the teams in
the PA2
but they are not. Instead, all teams belonging to the PA1 where the WI
is opened are listed.
What's the meaning of this? Do we want to let team members of a PA2 to
see the WI in PA1?
If not, do we want to open a WI in another PA than that where I'm
currently working? If so, then I should be able to see the teams in
PA2 and not in PA1.

Thank you,
Zica

Thank you Geoff.