DilOS4 Development Workflow is designed to support development and maintenance processes. There are several types of issues that are used in this workflow. They are:
...
Everybody who has Create Issue permissions can create an issue. However more full information about the bug, feature or task is helpful, but at least Description and Environment fields MUST be filled to create the issue. After this issue is placed to the backlog with OPEN status, it is automatically assigned to one of Development Lead and notification is sent to the assignee.
...
Development Lead can assign the issue to any Developer who can work on this issue. Or Developer can take this issue by looking through backlog and clicking on Assign to Me. After this he/she should change the issue status to Assign to developer → ASSIGNED. And now it is supposed that this person will work on this issue.
...
It is supposed that Developer works on the code when the an issue is in IN PROGRESS state.
...
All issues in RESOLVED state are ready for testing. This state for the quality assurance team is similar to OPEN state for the development team: Test Lead receives notification when any issue is put to this state and he can assign any Quality Assurance person for testing the issue. Test engineer can walk through the list of resolved issues and take it by clicking on Assign to Me as well. After this the issue should be transit to Verify → TESTING. After this the issue is treated as processing by the quality assurance team.
...