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="e9c6cc27ebcb1405-f6e88dff-4594453f-aacc83ac-0c8d9e2a9525751354d908c9"><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!]



What happens when an issue is created in Jira? The workflow for a given issue is dependent on what type of issue it is. The sections below describe the overall path an issue of given type will follow. Guidelines are also presented for the variours groups interactig with issues, as well as providing guidelines for such as Designers, Developers and QA, and discuss when and how to adjust an issue's status, resolution, versions, etc.


  • Issues is vetted for accuracy and completeness of information


  • Issues is vetted for accuracy and completeness of information

Feature Requests

  • Issues 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.

Contibuted Patches

  • On Issue creation
  • Implementation of Feature Requests
  • Notification