Assigned and Responsible Users

It is possible to set a Role as Responsible for a state in entity's Process Workflow. Say you can set Developer role as responsible for "In Dev" state and QA Engineer role as responsible for "Testing" state. These settings affect some filtering and visualization rules:

• On dedicated views, work items can be shown for Responsible people only and hidden for others
• Avatars of Responsible people on cards are shown in full color, while avatars of others are darkened
• Names of Responsible people in Assignments controls are shown in bold color

Views with work shown for Responsible people only

There are personal ToDo list views of two types in Targetprocess: filtered by Assignment and by Responsible role. There is a slight difference between them in place.

ToDo list filtered by Assignment

The views of this kind display all items you are assigned to, regardless of your role as well as a State the item is actually in. Once you’re assigned to a User Story, you’ll see it in your ToDo list. Usually the following filters are set to organize such views:

• ?AssignedUser.Where(it is Me)
• ?AssignedUser.Contains(Me)
• ?Assignments.Where(GeneralUser is Me)

The work item that belongs to some project (e.g. Project ABC) appears in the view of this kind when all of the following is true:

• The view is set up to display items from Project ABC
• You're included into the list of members of Project ABC
• You're included into the list of assigned users for the work item

ToDo list filtered by Responsibility

The views of this kind are a little bit smarter. Usually the following filter is set to organize such views:

?Responsible is Me

ToDo lists in Visual Studio IDE add-in and Eclipse IDE connector use exactly this built-in filter as well.

The work item that belongs to some project (e.g. Project ABC) appears in the view of this kind when all of the following is true:

• The view is set up to display items from Project ABC
• You're included into the list of members of Project ABC
• You are assigned to an entity under some role:
  • You're included into the list of assigned users for the work item AND
  • The work item is in the State that matches the Role you're assigned as
• OR you are assigned to the project under some role:
  • No users are assigned to the work item  AND
  • The work item is in the State that matches your Project Role

Roles set as Responsible for a Workflow state of an entity

The rules of Responsibility are configured the Workflow being set for your Project Process.

Let’s consider a Workflow example for User Stories:

A work item (that is, User Story) is displayed in the ToDo list only when the Role for this item you’re assigned to matches the Role designated as responsible for the State the item is currently in. Here is how it works:

It is not possible to set a Role as Responsible for a final workflow state.

More on Filters by Responsibility

The filter by Responsibility only works for “Me” and your personal ToDo list so far. It cannot display assignments for other particular person e.g. “'?Responsible is OtherGuy”. To see the responsibility overview for all team members we recommend you to use Work by People template with Hide not Responsible mashup installed.

?Responsible is Me filter shows the entities in state associated with role that matches your role regardless whether you are assigned or not. It is possible to process different cases with more codecise filters:

?Responsible is Me and Assignments.Where(GeneralUser is me)

It shows only tickets where you are assigned. It hides tickets where your role matches the state's role and nobody is assigned

And another one which gives negative option:

?Responsible is Me and not Assignments.Where(GeneralUser is me)

It shows only tickets where your role matches the state's role and nobody is assigned - and you are not assigned as well.

Cases and rules can be combined together and this give your filters a real power and flexibility. Find useful examples in dedicated article.

Responsibility by Team membership