Project Area Restrict Read Access details - v3.0M6
Hello,
has anyone tried the feature for restricting the read access for a WI (mentioned as "More Flexible Access Control" - WI 101846).
I'm trying to use it creating a WI in a "PA1" and restricting a different "PA2" access to it. The problem comes when I try find the WI from "PA2" ... I can't locate it from a query so I'm not able to see whether this access restriction is working for this case scenario.
am I doing smth wrong? Any advice will be welcome.
Thanks in advance for the help.
Regards,
Jorge.
has anyone tried the feature for restricting the read access for a WI (mentioned as "More Flexible Access Control" - WI 101846).
I'm trying to use it creating a WI in a "PA1" and restricting a different "PA2" access to it. The problem comes when I try find the WI from "PA2" ... I can't locate it from a query so I'm not able to see whether this access restriction is working for this case scenario.
am I doing smth wrong? Any advice will be welcome.
Thanks in advance for the help.
Regards,
Jorge.
2 answers
Hi,
I've found a way of using this feature in 3.0M6. I'll try explain it ...
I have created 3 PAs, let's say PA1, PA2, PA3. PA2 and PA3 have as members the users belonging to that particular teams plus the "management" users. This way all users will work on PA1 and this "cross belonging" is just to make management users able to see all WIs and the PA2 and PA3 users just see their team assigned work.
So summarizing, PA2 and PA3 are just dummy PAs that serve as "user lists" to restrict WIs visibility.
As this is a very ugly approach and could lead to a great number of PAs with no actual function; can you think of a better way of performing the same with actual M6?
Will be any neater way of performing the same in future 3.0 GA? (maybe one of the features mentioned in WI 60372) Any details of how such feature will be very helpful.
Thanks!
Regards,
Jorge.
I've found a way of using this feature in 3.0M6. I'll try explain it ...
I have created 3 PAs, let's say PA1, PA2, PA3. PA2 and PA3 have as members the users belonging to that particular teams plus the "management" users. This way all users will work on PA1 and this "cross belonging" is just to make management users able to see all WIs and the PA2 and PA3 users just see their team assigned work.
So summarizing, PA2 and PA3 are just dummy PAs that serve as "user lists" to restrict WIs visibility.
As this is a very ugly approach and could lead to a great number of PAs with no actual function; can you think of a better way of performing the same with actual M6?
Will be any neater way of performing the same in future 3.0 GA? (maybe one of the features mentioned in WI 60372) Any details of how such feature will be very helpful.
Thanks!
Regards,
Jorge.
I've found a way of using this feature in 3.0M6. I'll try explain it
..
I have created 3 PAs, let's say PA1, PA2, PA3. PA2 and PA3 have as
members the users belonging to that particular teams plus the
"management" users. This way all users will work on PA1 and
this "cross belonging" is just to make management users able
to see all WIs and the PA2 and PA3 users just see their team assigned
work.
So summarizing, PA2 and PA3 are just dummy PAs that serve as
"user lists" to restrict WIs visibility.
As this is a very ugly approach and could lead to a great number of
PAs with no actual function; can you think of a better way of
performing the same with actual M6?
Will be any neater way of performing the same in future 3.0 GA? (maybe
one of the features mentioned in WI 60372) Any details of how such
feature will be very helpful.
Please see the discussion in
https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/105274
--
Regards,
Patrick
Jazz Work Item Team