- 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, 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="58355a6547860235-0fb853a7-4c374de3-bbda93d3-fbc5ada499143a8b423d0e0e"><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!]
- QA personnel select an appropriate issue from the list of issues "QA Awaiting Verification".
- An attempt is made to verify the issue.
- If it passes verification, then it is Closed.
- If it fails verification, then it is Reopened.
- If is not clear to whom the issue needs to be re-assigned, then assign it to default.
- Some issues can not be easily verified and may require special testing conidtions or input from developers, and further discussion is conducted as necessary.
You can subscribe to filters in Jira and receive an email summary of the filter's contents at a time interval you specify.
For folks interested in a daily summary of updates in the Sakai project in Jira, you should subscribe to the "Updated in Last 24 Hours" filter. (Note that the time of day when you subscribe is the time of day when Jira will send you digest, so might want to subscribe to the filter early one morning.)
- Automated notifications
Jira can also send you 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 email@example.com.