Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

How Jira is Used in Sakai

This page outlines the general procedures, practices, and definitions adopted by the Sakai community in using Jira (and Confluence) to help manage our design and development efforts.

Definitions

Issue Types

We are currently using the following Jira Issue Types to track work for Sakai:

  • test!http://bugs.sakaiproject.org/confluence/images/icons/web_16.gif!Bug - an error in design or implementation which directly impedes a user from achieving the 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
  • Contributed Patch - a community-contributed patch to particular version of sakai. use at your own risk! 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.

Status

Resolution

Version Management:

  • Affects Version - generally speaking, the version in which an issue is observed
    • Bug - version in which a bug has been identified
    • Task - not required, however, references to the capabilities of an existing version of Sakai may help provide context
    • Feature Request - not required, however, references to the capabilities of an existing version of Sakai may help provide context
    • Contributed Patch - version(s) of Sakai to which the patch can be applied
  • Fix Version - generally speaking, the version in which an issue is resolved
    • Bug
    • Task
    • Feature Request
    • Contributed Patch

Security Issues

  • visible only to committers and issue reporter

Workflow

  • On Issue creation
  • Implementation of Feature Requests

Notification

  • No labels