Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 50 Next »

How Jira is Used in Sakai

This page outlines the general procedures, practices, and definitions adopted by the Sakai community for using Jira.


Issue Type

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="f08b9c92-cd99-4817-b4b3-822e40683155"><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!]




Definition for Sakai


Issue is under consideration.

In Progress

Issue is actively being worked on.


Issue was thought to be completely addressed, however, it failed verifcation and needs further work.


Issue has been addressed and it is ready for testing.


Work on issue is complete and it has passed testing.



Definition for Sakai


Issue is under consideration and/or actively being worked on.


Issue has been addressed through changes to the design or code. Specific details code changes can be accessed through the "Subversion Commits" tab.

Won't Fix

Issue will not be addressed because it does not match project goals. Such an issue might become a Feature Request.


Issue turned out not to be a problem. Such an issue might result in a Feature Request or become an entry in the Sakaipedia if it is a common point of confusion.


Issue is a duplicate of a previously submitted issue. A link to the original issue is added so that progress on the issue can be easily accessed.


Not enough information has been provided to achieve a full understanding of the issue. An effort is made to obtain further information from the Reporter before resolving and abandoning an issue in this manner.

Cannot Reproduce

Issue cannot be reproduced. Generally these are issues solved as a by-produced of other work.


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

  • Affects Version - Version in which an issue is observed.
  • Fix Version - Version in which an issue is resolved.

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

Issue Type

Affects Version

Fix Version


Version in which bug was identified.

Version in which bug is expected to be or has actually been resolved.


Not required, but may provide useful context for comments on the issue.

Version in which new capabilitity is expected to appear or has appeared.

Feature Request

Not required, but may provide useful context for comments on the issue.

Not applicable. (Note that Feature Requests selected for implementation are converted to one or more Tasks for tracking the actual work.)

Contributed Patch

Version to which the patch can be applied.

Not applicable. (Note that a link is created to the Bug or Feature Request for tracking Sakai work on the issue.)

Security Issues

  • visible only to committers and issue reporter


  • On Issue creation
  • Implementation of Feature Requests
  • Notification
  • No labels