Versions Compared

Key

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

...

Tip
titleJira Account

You can search and view content in Jira without an account, however, you do need one to comment on or post information. Jira accounts are available through self-registration. (Note that Jira and Confluence share acccountsaccounts, however, Jira/Confluence accounts are separate from Collab accounts.)

...

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/Requirement

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="9563da9f061e6dab-9b447cc9-4526476a-be8b9f39-7d7f78905c5b5a486c5e22fd"><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 original issue in order to track Sakai's work on the issue. [Use at your own risk!]

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

Branch

An experimental branch of code, which may or may not be merged back into the main code after the experiment completes; identified in SVN by a branch named with the Jira Key.

...

Resolution

Definition for Sakai

Unresolved

Issue is under consideration and/or actively being worked on.

Fixed

Issue has been addressed through changes to the design or code. When viewing an issue, the "Subversion Commits" tab provides specific details regarding code changes.

Won't Fix

Issue will not be addressed because it does not match project goals.

Non-Issue

Issue turned out not to be a problem with Sakai.

Duplicate

Issue is a duplicate of a previously submitted issue. A link to the other issue is added so that progress on the issue can be easily accessed.

Incorporated

Issue has been incorported incorporated into another issue. A link to the other issue is added so that progress on the issue can be easily accessed.

Incomplete

Not enough information has been provided to identify the issue.

Cannot Reproduce

Issue cannot be reproduced.

...

  1. Issue is Opened.
  2. Issue is vetted for accuracy and completeness of information and linked to related issues.
    • (Duplicate) If it duplicates a previous issue, then the newly opened issue is:
      1. Linked to the original issue as "duplicates"
      2. Commented with a note to look at the linked-to issue to track further progress
      3. Closed with a Resolution of "Duplicate"
      4. Target and Fix Version and should be set to "Unknown"
    • (Incorporated) If it is incorporated into a previous issue, then the newly opened issue is:
      1. Linked to the original issue as "incorported incorporated by"
      2. Commented with a note to look at the linked-to issue to track further progress
      3. Closed with a Resolution of "Incorporated"
      4. Target and Fix Version and should be set to "Unknown"
    • (Non-Issue) If it turns out that the issue was the result of a mis-understanding of how Sakai operates, then:
      1. An effort is made to clarify the situation.
      2. If the mis-understanding does not suggest a design flaw, then it is Closed with a Resolution of "Non-issue"; otherwise, the design flaw could be captured to Bug or Feature Request.
      3. Target and Fix Version should be set to "Unknown"
    • (Incomplete) If insufficient information is provided to describe the issue, then:
      1. An effort is made to obtain additional information.
      2. If insufficient information is provided in a reasonable time-frame, then the issue is closed with a Resolution of "Incomplete"; issue can always be Reopened.
      3. Target and Fix Version should be set to "Unknown"
    • (Cannot Reproduce) If the issue cannot be reproduced on one of the QA test servers, then:
      1. An effort is made to obtain additional information.
      2. If insufficient information is provided in a reasonable time-frame, then the issue is closed with a Resolution of "Cannot Reproduce"; issue can always be Reopened.
      3. Target and Fix Version should be set to "Unknown"
  3. Issue is assigned to the appropriate project lead.
    **Further vetting, as above, may be necessary for particularly complex issues.
  4. Initial estimates of the scope of the bug and the resources required to address it are made and the reported Priority and Target Version are updated accordingly.
  5. An issue may be re-assigned to others or Watchers added to facilitate discussion of its resolution. The Priority, Target Version, Components, etc. should also be updated as necessary as discussion around the issue evolves.
  6. Assignee Resolves issue with relevant Resolution when work is completed, and updates Fix Version to "Nightly/SVN-Trunk" (or other version in special circumstances.)
    • (Fixed) Most issues that reach this stage are resolved and their resolution is set to "Fixed".
    • (Won't Fix) Some issues are identified as conflicting with the expectations of the currently adopted design or represent technical "impossibilities" and resolved as "Won't Fix", or they can be Moved to become Feature Requests for future consideration.
  7. QA team verifies resolution of issue.
    • If it passes verification, then it is Closed.
    • If it fails verification, then it is Reopened and re-assigned for further work.

...

  1. User posts an issue in Jira.
    • The Affects Version should be set to the released version on which the instance of Sakai is based.
    • The Target Versions and Fix Version should be initially reamin remain set to Unknown. The project teams, when they have a chance to evaluate your issue, will set this to reflect an estimate of when they believe they will be able to address the issue.

...

  • All issues resolved as "Fixed" should have a Fix Version set, which generally is just "Nightly/SVN-Trunk". A tag or branch version should only be added to the Fix Version field when the fix is actually merged in.
  • All issures issues resolved with a resolution other than "Fixed" should not have a Fix Versions set. (The Fix Version should be "Unknown".)
  • When resolving an Issue as Fixed, you generally want to set the Fix Version to Nightly/SVN-Trunk, as that is where you are typically fixing an issue.