Versions Compared


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


Issue Type

Definition for Sakai


An error in design or implementation which directly impedes a user from achieving their expected result.


A new capability being added to Sakai.

Feature Request

A desired capability, which may be selected for implementation in a future release of Sakai.

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="3838a58f7a75fe12-f9fcaeb2-46444529-bd1d93b3-a886a68ae2657ecdde5c9cf8"><ac:plain-text-body><![CDATA[

Contributed Patch

A community-contributed patch to a particular version of sakai. The origin of such issues may lie in Bugs or Feature Requests which Sakai has not yet evaluated for implementation. Under such circumstances a linked issue is generally created by cloning the orignal issue in order to track Sakai's work on the issue. [Use at your own risk!]



  1. Issue is vetted for accuracy and completeness of information.
  2. An initial estimate of the scope of the bug and the resources required to address it is made, which leads to an initial Priority and Fix Version.
  3. Issue is a assigned to the appropriate individual.
  4. An issue may be assigned to others or Watchers added to facilitate discussion of its resolution. The Priority, Fix Version, Components, etc. may also be appropriately updated.
  5. Assignee Resolves issue appropriately with relevant Resolution when work is completed, and updates Fix Version as necessary.
  6. QA team verifies resolution of issue and Closes the issue if it is appropriately resolved, otherwise the issue is Reopened. (QA verification only occurs against releases, not against the SVN Trunk.)


  • Issue is vetted for accuracy and completeness of information.

Feature Requests

  • Issue is vetted for accuracy and completeness of information
  • What exactly happens next to Feature Requests is being determined as part of our ongoing development of a community requirements process.