|
Introduction
|
Top Previous Next |
| · | The project administrators may define a set of change states that determines the change lifecycle.
|
| · | The project administrators assign specific workers, or worker groups, that are responsible to handle changes in every state. Optionally, the assigned workers get email notifications whenever a pending change is available.
|
| · | All changes checked-in to the project are assigned to an initial state determined by the project administrators.
|
| · | The project administrators determine the change control range. Normally, control range is for all changes performed to the last release until current date.
|
| · | Every worker may view tasks assigned to him or her in order to evaluate the changes' status. Workers may promote the change to the next state, or demote it to the previous state.
|
| · | Administrators may view the current project change status. Various reports are available as well.
|
| · | Administrators may assign any state to a change. This bypasses the normal promote/demote procedure.
|
| · | Administrators may undo a change. This is useful to disregard a change that is not fully tested or in conflict with other changes. An undone change can be restored at any point.
|