Jira and Confluence share user accounts. You do not need an account to view content in these systems, however, you do need one to comment on or post information. You can request an account from firstname.lastname@example.org. (
Note that your Jira/Confluence account is completely separate from a Collab account, http://collab.sakaiproject.org, and a Sakai website account, http://www.sakaiproject.org; currently you need a separate username and password for each system.)
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.
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="7982dac4bc2e6605-7ea296f1-4c094f07-95289f74-0544bd3713e8b1f75712a138"><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 orignal issue in order to track Sakai's work on the issue. [Use at your own risk!]