It's all about the answers!

Ask a question

Is it possible to restrict the visibility of "Work Item Type" for members of particular team area alone ?


Chid . (2072854) | asked Mar 14 '14, 3:39 a.m.
edited Mar 14 '14, 3:43 a.m.

SEPG (Software Engg Process Group) & Audit group wants to track some data for all the projects based for reporting purposes; Attributes are created for this data. 

Portfolio manager of a Portfolio A wants to track additional data for his team alone. Portfolio Manager of Portfolio B wants to track some data for his project alone. In this case, we created Defect-A that suites the requirement of SEPG & Portfolio A; Defect-B that suites the requirements of SEPG & Portfolio B. Editor changes for Defect-A & Defect-B.

Attributes defined by SEPG are placed in both Defect-A & Defect-B. Hence SEPG can generate one report encompassing all the portfolios and each portfolio manager can generate his own report for his own data.

When the user creates a Defect, he sees both Defect-A & Defect-B as Work Item types. When there are 10 Portfolios, this becomes messy. User is confused on which Defect type to use.

Portfolio A & Portfolio B are separate Team Area. Members of Portfolio A will use only Defect-A and will not use Defect-B. Is it possible to restrict the visibility of Work Item Type to members of particular team area alone ?

Any other solutions are solicited.


Comments
Krzysztof Kaźmierczyk commented Mar 14 '14, 4:05 a.m. | edited Mar 14 '14, 5:16 a.m.

Hi Chidambaram,
Have you heard about restrict workitem visibility feature? You can find more details here: https://jazz.net/library/article/554

Let us know if that helps.


Chid . commented Mar 14 '14, 4:37 a.m.

Article 554 talks about restricting Work Item Access by enabling Category Visibility. But I am asking about restricting the visibility of Work Item Type itself. In the browser, Work Items menu should show only the "Work Items Types" which the user can create. Valid Work Item Types should be defined for a Team Area.

One answer



permanent link
Krzysztof Kaźmierczyk (7.4k34896) | answered Mar 14 '14, 5:20 a.m.
Chidambaram,
There is no such function in RTC. But my understanding of the tool is that you should use separated project areas for each portfolio. Then you will have the behavior which you already want to.

Is there any reason why you are not using separate project areas?

Comments
Chid . commented Mar 14 '14, 7:07 a.m.

Keep the number of projects less for cleanliness and ease of maintenance.

I will recommend one RTC, one RRC & one RQM project for an organization ideally. But practically we need more than one.


Krzysztof Kaźmierczyk commented Mar 14 '14, 8:09 a.m.

Chidambaram,
To be honest it is really difficult to find a case when managing one single PA is easier than managing the couple of them. Could you elaborate what is the difference for you here?


Geoffrey Clemm commented Mar 14 '14, 1:56 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

One of the main reasons to have a single project area is that queries are scoped to a single project area.   But this also highlights the downside of providing custom work item types for each stakeholder group, because that makes it hard for one team to understand the information being generated by another team.   Having a common set of work item types for all teams encourages each team to re-use the shared work item types, rather than creating a custom one of their own.

Your answer


Register or to post your answer.