Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Team specific work item types

Hello,
In my project area I have two teams and two work item types. Would it be possible to configure it the way that each team would only see and be able to create only one work item type and not the other? For instance I have Team1 and Team2 and Defect and Task work item types. So the goal is to make Team1 to be able to see ( and create ) Defects only in RTC client and Team2 to see the Tasks only.
Thanks,
Anatoliy

0 votes


Accepted answer

Permanent link
You can control who can create work items of a specific set of types in a role-based way ... i.e. you can have a task-creator role, and assign that to the people that are allowed to create tasks, and a defect-creator role, and assign that to the people that are allowed to create defects.
You also can control who can see existing work items, by indicating that work items assigned to a particular team should only be visible to members of that team.
But I am not aware of any out-of-the-box way of hiding the existence of a particular work item type from just some teams in a project area but not others.
Anatoliy Khludov selected this answer as the correct answer

0 votes


3 other answers

Permanent link
workitems are project wide.

you can limit visibility by team but its ALL workitems for a team..
team A can't see Team B's work, and vice versa.. but its ALL workitems

0 votes


Permanent link
It seems there is no direct way to restrict a whole work item type but you can try either by Restricted Access presentation or by creating WorkItem Categories to restrict access to work items.

Although not tested, but you may try to combine workitem categories and use calculated value script to automatically fill the FiledAgainst attribute depending on the workitem.Type

0 votes


Permanent link
Thanks Geoffrey, Sam and Indradri for your answers! This pretty much confirms the behavior that I'm seeing. I just wanted to have as much isolation as possible between teams in one project to avoid confusion.

0 votes

Your answer

Register or log in 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.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 6,129

Question asked: Apr 30 '13, 4:06 p.m.

Question was seen: 5,010 times

Last updated: Apr 30 '13, 8:31 p.m.

Confirmation Cancel Confirm