Versions Compared


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


  • Users who want to submit issues should review the Workflow.
  • If you have questions regarding Jira, please send them to
  • You can search and view content in Jira without an account *, however, you do need one but one is required to comment or create issues. Jira accounts are available through self-registration. (Note that Jira and Confluence share accounts).

Related pages: Maintenance Branch Guidelines


| Feature Branches


| Jira Branches


Basic Workflow


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, for inclusion in a future release of Sakai; ideas that come with resources interested in implementing them are more likely to be developed than those offered with the hope that someone else will step forward to do the work.

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="3dba5f02405b2ba2-4a475e45-48b84878-8b30b9b0-514bae50a54ba38c88218acb"><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 original issue in order to track Sakai's work on the issue. [Use at your own risk!]



An experimental branch of code, which may or may not be merged back into the main code after the experiment completes; identified in SVN by a branch named with the Jira Key.