It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,876

question asked: Jan 30 '14, 1:51 p.m.
question was seen: 3,518 times
last updated: Feb 03 '14, 5:57 p.m.

Related questions

Restrict Work Item Access

0
John S F Lander (90●19●42) | asked Jan 30 '14, 1:51 p.m.
There are many question and answers on this but not quite got to the answer that I am looking for !!!

In a PA, I have nested teams and categories

Project Area
           Team 1
                     Team A
                     Team B
           Team 2
                     Team
So basically by turning the Restrict Work Item Access on at the category on the PA and associating each Category with their Team, I would have expected that if a user was added at the higher level, ie Team 1, then they could view and create WIs at the Team A & Team B level but find you have to be added to both Team A and Team B, the problem with this, is that you can assign WIs to users that are only supposed to be viewing the WI in that Team
            

2 answers

Most liked answers ↑|Newest answers|Oldest answers

1
permanent link
Geoffrey Clemm (30.1k●3●30●35) | answered Jan 31 '14, 3:19 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
There is no way currently to say "restrict access to this work item to members of this team area and members of any parents of this team area".   You should feel free to submit an RFE requesting this functionality.
Comments
John S F Lander commented Jan 31 '14, 3:41 a.m.

Hi Geoff,

Just to clarify.

If I am in the Parent Team, I would want to see the WIs in the child Team Area even if I wasn't a member of that Child Team

Geoffrey Clemm commented Feb 03 '14, 5:57 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

Understood. 

0
permanent link
Piotr Aniola (3.7k●1●17●38) | answered Jan 31 '14, 4:06 a.m.
Please check the following library article that describes current behavior:
https://jazz.net/library/article/837
In shortL
  • Note that the visibility based on category was initially meant for root-level team areas. In a hierarchy of team areas, the visibility heritage then works in a bottom-up manner (see References).
  • The different types of access restriction features are not meant to be used in combination. If you really need to restrict access to some work items, choose the one that better fits your needs.

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.