- A user (anyone) creates an Issue (please see #Create Issue Detailed Instructionsfirst first)
- Issue is automatically assigned to a Awaiting Review status
- Sakai Core team member verifies the issue for accuracy (i.e. is it an actual issue) and completeness of details.
- Complete and valid issues are set to status Open and assigned to a user or group (e.g. Samigo Team or Sakai Core Team) who can resolve it.
- The team member may resolve the issue as Duplicate , Incomplete , or Cannot Reproduce if appropriate (see #Resolution).
- Assignee selects Start ProgressProgress and begins to work on the issue (as time and priorities allow)
- Assignee selects Stop Progress if they are not going to work on the issue anymore for a few days and it is not resolved
- Assignee sets the issue to Resolved with the relevant #Resolutionwhen when work is completed
- For tasks, if there is nothing explicit for the QA team to test, then the issue is Closed without testing.
- QA team selects Start QAQA and begins verifying the issue
- QA team member selects Stop QA if they are not going to complete the testing on the issue within a short time frame
- QA team verifies resolution of the issue and adds a comment with details of the testing results and process.
- If verification fails, then it is Reopened for further work (automatically re-assigned to the user who resolved it)
- If verification succeeds then QA marks the status as Verified (indicating it has been Tested)
- Release Manager merges the issue (if it is a bug) to previous supported and affected releases
- The associated version merge status is set to Resolved (see #MergeStatus )
- The issue is Closed by the Release Manager when the last merge has been completed