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 Type
- Security Issues
We are currently using the following Jira Issue Types to track work for Sakai:
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.
Desired capability, which may be selected for implementation in a future release of Sakai.
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.
- Affects Version - generally speaking, the version in which an issue is observed
- Bug - version in which a bug has been identified
- Task - not required, however, references to the capabilities of an existing version of Sakai may help provide context
- Feature Request - not required, however, references to the capabilities of an existing version of Sakai may help provide context
- Contributed Patch - version(s) of Sakai to which the patch can be applied
- Fix Version - generally speaking, the version in which an issue is resolved
- Feature Request
- Contributed Patch
- visible only to committers and issue reporter
- On Issue creation
- Implementation of Feature Requests