It's all about the answers!

Ask a question

Multiple Filed against for a workitem in RTC

vishnudharan manivannan (1183642) | asked Mar 07 '16, 6:21 a.m.

Hello team,

We use RTC 5.0.2 . I have a business use case to have multiple filed against in RTC. Let me give an example scenario.

There are 5 team areas and each team area is associated with a workitem category.

Restrict workitem access is also enabled.

Now a workitem should be part of 3 team areas and it should be visible only to those users who are part of at least 1 team from these 3 team areas it is filed against.

Is something like this possible in RTC ?

Please let me know your thoughts.

Vishnu M

Accepted answer

permanent link
Ralph Schoon (63.2k33646) | answered Mar 07 '16, 8:21 a.m.
edited Mar 07 '16, 8:31 a.m.
You can customize RTC and add one or more custom attributes of type Category. These will only have informational character however, as far as I know. (The work item can likewise only be owned by one user. You can add attributes to be filled with other users, but that will have no influence on the built in automation.)

A work item can only be assigned to one category. A category can only be assigned to one team area (which can have parent areas). A work item can only be owned by on team (or project) area. The owning area can have parent areas.

The restricted work item access you mention above is automated based on the one built in attribute filed against. If restricted access based on category is switched on, the server automatically sets the attribute "Restricted access" which actually is used to control the restricted access. This automatic setting will only depend on the one built in "Filed against" attribute.

It would be possible to use restricted access to work items and use Access groups to control who has access to the work item and who not. An Access group can contain multiple team areas. This could, with potential custom automation, help to solve the visibility issue. It won't solve planning issues, should you also try to use multiple categories for planning.

See and the related posts for a discussion around automation for restricted access.

vishnudharan manivannan selected this answer as the correct answer

vishnudharan manivannan commented Mar 09 '16, 12:53 a.m. | edited Mar 09 '16, 12:54 a.m.
Hello Ralph,

Thanks for your suggestion. 

we went through the article and we have a confusion as of how to implement in our scenario.

To explain again.

We will have a workitem which has an enumeration list value. User can set this field to multiple enumeration values (Each enumeration value is a team area).

Now example if  a task has the enumeration list value set to Team 1 & Team 2.

Then when a user tries to access the workitem, RTC should allow the user to read the workitem if he is part of any 1 team area user list.

any thoughts on how we can get around this scenario ?

Thanks again,
Vishnu M

Geoffrey Clemm commented Mar 09 '16, 6:44 p.m.

As Ralph points out, you cannot have more than one filed-against values for a given work item, so you cannot use that mechanism to specify that a given work item can be viewed by multiple teams.   Something that would work would be to create an access group that contains Team1 and Team2, and then restrict access for that work item to that access group.

vishnudharan manivannan commented Mar 10 '16, 1:10 a.m.

Thanks Ralph & Geoff for your suggestions.

Appreciate it!

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.