Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Issue Type

Definition for Sakai

Bug

An error in design or implementation which directly impedes a user from achieving their expected result.

Task

A new capability being added to Sakai.

Feature Request

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="37c1c591b15936a2-321bb8b0-43d14313-8df49331-614365005a8715587754b983"><ac:plain-text-body><![CDATA[

Contributed Patch

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!]

]]></ac:plain-text-body></ac:structured-macro>

...

In practice, the Jira Priority field is generally only important to utlized by Sakai at two times: during prioritization of requirments for implementation and when making decisions on what will actually appear in a release. Initial priorities, when an issue is first reported, may be changed to reflect those needs.

Priority

Definition for Sakai

Blocker

Issues that must be resolved before a release.

Critical

Issues that should be resolved before a release. ...

Major

Issues that may be resolved before a release. ...

Minor

...

Image Added Trivial

Issues that might be resolved before a release.

Image Removed Trivial

Issues that

Anchor
Security Issues
Security Issues
Security Issues

...