- 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="5a100c33163377cc-223aa593-450049a6-a2839d15-2e2c6c677083598eb6b6d538"><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!]
Jira can also send on-event notification emails, such as whenever an issue is created, updated, resolved, closed, etc. If you are interested in receiving such emails, then please contact Peter A. Knoop.
- When resolving an Issue as Fixed, set the Fix Version to Nightly/SVN-Trunk. (Exception: if you are managing your own branch for your project.)
- All issues resolved as "Fixed" should have a Fix Version set.
- All issures resolved with a resolution other than "Fixed" should not have a Fix Versions set. (The Fix Version should be "Unknown".)