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="5932cddac0a61bf1-22159b55-42854dac-be6c8e92-7b3fdd52c79e2518efe5e051"><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!]




Every Jira issuce can have Each Jira issue has an Affects Version and a Fix Version. Generally speaking Sakai uses these versions to indicate:


Both of these versions, however, are not necessarily meaningful for all issue types. The table below summarizes how these versions are interpreted applied in Sakai for the various issues types.