Click the Permissions tab to edit permissions, by role, for the following:

When the issue is important, and must be carefully tracked, enable workflow process management. A simple and flexible process engine workflow is integrated into the trackers to allow modeling of business process workflow. Trackers can be used with or without workflow. Trackers can inherit a workflow from other trackers or use their own workflow. The workflow can be customized. See State Transitions.

Define the workflow state diagram roles' transition permissions on the State Transitions tab. The workflow transitions define the transitions between states, and which roles have permission to enact each transition-type.

You can edit the field access permissions for project members on the Fields tab in tracker customization. There is a permission column in the fields table; click the field's permission cell content to edit permission. Access permissions are a three-dimensional matrix of permissions, with the axes of roles, issue fields and status. For every status, there is table that shows field-access permissions for each role.

Each member's view or edit access to a field is defined for each status of the issue. Define a default value for a field, or make the field required, in the field Access definitions.

The state transition window handles the transition between the source status and the target status of a tracker item.

If the user initiating the state transition has permission to edit a field in either the source status or the target status, that field is editable in the transition window. After you click Save in the transition window, Codebeamer assigns the target status to the item. This behavior ensures that the user who transitions the item can handle the mandatory fields.

For more information about transitioning items, see State Transitions.