Sakai uses Atlassian's Jira software for issue management. It is used to track a variety of issues, including bug reports, suggestions for new functionality, tasked work, and community contributions. Outlined below are the general practices, procedures, and definitions adopted by the Sakai community for using Jira. If you have questions regarding Jira, please send them to firstname.lastname@example.org.
Jira and Confluence share user accounts. You do not need an account to You can search and view content in these systemsJira without an account, however, you do need one to comment on or post information. You can self-register for an account by clicking on the "Sign-Up" link in the login dialog. Note that your Jira/Confluence account is completely separate from a Collab account, http://collab.sakaiproject.org. You need a separate username and password for each system.Jira accounts are available through self-registration. (Note that Jira and Confluence share acccounts, however, Jira/Confluence accounts are separate from Collab accounts.)
- General Workflow
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.
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="2030d3f3965016cb-551ce350-45484584-8079aa93-2d61f16c5f7f14f25aa9b375"><ac:plain-text-body><![CDATA[
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!]