Flow of Responsibility
You can define responsibilities for work items in member fields, for example:
• Assigned to: The project or role members responsible for doing the work.
• Supervisor: The project or role members responsible for supervising the work.
These responsibilities may change throughout the lifecycle of a work item, which affects the flow of work and responsibility from one set of users to another.
Codebeamer allows you to control the flow of responsibility by restricting the Allowed valuesfor fields, which can limit changes to values in a certain status.
For example, the allowed values for the field Assigned to by status:
You can assign a reallocation of responsibility upon entering a specific status.
A graphical representation of a flow of responsibility could be shown as an UML Activity Diagram with Swimlanes, where each swim lane represents a role, the nodes represent states, and the arrows are state transitions.
For example, a simple bug handling process:
Figure: A Simple Bug-Handling Process
This example shows the core workflow only. You would need to define more states and transitions, for example, to reject fixes that did not pass quality tests.