How Jira is Used in Sakai

This page outlines the general procedures, practices, and definitions adopted by the Sakai community in using Jira (and Confluence) to help manage our design and development efforts.


Issue Types

We are currently using the following Jira Issue Types to track work for Sakai:


Issue Type

Definition for Sakai


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



New capability being added to Sakai.


Feature Request

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


Contributed Patch

Community-contributed patch to particular version of sakai. Use at your own risk! 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.



Version Management:

Security Issues