It's all about the answers!

Ask a question

Is it possible to restrict visibility of work items to certain teams

Ankit Jain (6423639) | asked Jul 24 '12, 2:45 p.m.
retagged Jul 25 '12, 9:06 p.m. by Millard Ellingsworth (2.5k12431)
Is this possible in RTC?

We need to restrict work items on team basis. For instance,  when two work items are assigned to two different teams, only those in the team should be able to access the respective work items. The flow will be  -

a) User selects a group name while creating a work item.

b) Work item is assigned to team. None other than the creator and the team will have access to the created item.

c) Only the users in the assigned team (not even the creator) will be able to update the 'Owned By' and 'Priority' attributes.


Our asks are -

1) How to implement the above flow?

2) While using 'Restricted Access', the drop down displays the project areas. How to display the team areas rather than project areas?

3) While 'Restricted Access' was added in one presentation, all presentations were automatically updated with this (Restricted Access). How to restrict this to particular items only?

4) How to exclude some of the project areas from appearing in 'Restricted Access' drop down? We don't want all to appear here.

Accepted answer

permanent link
David Olsen (5237) | answered Jul 24 '12, 6:53 p.m.
To restrict read access to work items owned by a team, you should use the "Restrict Work Item Access" property on the work item category.  If a category is marked as having restricted access, then any work item filed against that category will be visible to the members of the team area that the category is associated with.

This comes close to getting what you want, but not quite.  The problem is that the creator of the work item can't see the work item (unless he is also a member of the correct team).  Which means that the user can't even file the work item against that category; RTC will fail with an error.

I don't know of a practical way for a work item to be visible to the team that owns and to the creator but not to anyone else.

-- David Olsen, IBM Rational, Jazz Process Team
Ralph Schoon selected this answer as the correct answer

Your answer

Register or to post your answer.