Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  1. A user (anyone) creates an Issue (please see #Create Issue Detailed Instructionsfirst)
    • Issue is automatically assigned to a Awaiting Review status
  2. CLE 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 CLE Team) who can resolve it.
    • The team member may resolve the issue as Duplicate, Incomplete, or Cannot Reproduce if appropriate (see #Resolution).
  3. Assignee selects Start Progressand 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
  4. Assignee sets the issue to Resolved with the relevant #Resolutionwhen work is completed
    • For tasks, if there is nothing explicit for the QA team to test, then the issue is Closed without testing.
  5. QA team selects Start QAand 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
  6. 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)
  7. 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
    • The issue is Closed by the Release Manager when the last merge has been completed


Coming soon!

Image Added

(Exported from JIRA Sakai CLE Workflow on 31 March 2012 - AZ)


Create Issue Detailed Instructions
Create Issue Detailed Instructions
Create Issue Detailed Instructions