JIRA - Local help

JIRA tracks issues, which can be bugs, feature requests, or any other tasks you want to track.

Each issue has a variety of associated information including:

  • the issue type
  • a summary
  • a description of the issue
  • the project which the issue belongs to
  • components within a project which are associated with this issue
  • versions of the project which are affected by this issue
  • versions of the project which will resolve the issue
  • the environment in which it occurs
  • a priority for being fixed
  • an assigned developer to work on the task
  • a reporter - the user who entered the issue into the system
  • the current status of the issue
  • a full history log of all field changes that have occurred
  • a comment trail added by users
  • if the issue is resolved - the resolution
Issue Types

JIRA can be used to track many different types of issues. The currently defined issue types are listed below. In addition, you can add more in the administration section.

For Regular Issues
Bug
A problem which impairs or prevents Moodle from functioning correctly.
Improvement
An enhancement to an existing Moodle feature.
New Feature
A new Moodle feature which has yet to be developed.
Release Test
A set of tests for a single release
Task
A task that needs to be completed. Tasks usually refer to work that must be done outside the product.
For Sub-Task Issues
Functional Test
A test of a single Moodle feature
Sub-task
Issues are sometimes broken into multiple sub-tasks.
Priority Levels

An issue has a priority level which indicates its importance. The currently defined priorities are listed below. In addition, you can add more priority levels in the administration section.

Blocker
Blocks development and/or testing work, production could not run.
Critical
Crashes, loss of data, severe memory leak.
Major
Major loss of function.
Minor
Minor loss of function, or other problem where easy workaround is present.
Trivial
Cosmetic problem like misspelt words or misaligned text.
Statuses

Each issue has a status, which indicates the stage of the issue. In the default workflow, issues start as being Open, progressing to In Progress, Resolved and then Closed. Other workflows may have other status transitions.

Open
The issue is open and ready for the assignee to start work on it.
In Progress
This issue is being actively worked on at the moment by the assignee.
Reopened
This issue was once resolved, but the resolution was deemed incorrect. From here issues are either marked assigned or resolved.
Resolved
A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.
Closed
The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.
Passed
The test passed
Failed
The test failed and needs to be re-run once the problem is fixed
Obsolete
This test no longer makes sense
Resolutions

An issue can be resolved in many ways, only one of them being "Fixed". The defined resolutions are listed below. You can add more in the administration section.

Fixed
Bug has been fixed; a code change will be checked into CVS.
Won't Fix
The problem described is an issue which will never be fixed.
Not a bug
This issue is not a bug; was logged in eror.
Duplicate
The problem is a duplicate of an existing issue.
Incomplete
More information is needed to understand this bug.
Cannot Reproduce
All attempts at reproducing this issue failed, or not enough information was available to reproduce the issue. Reading the code produces no clues as to why this behavior would occur. If more information appears later, please reopen the issue.
Deferred
The resolution to this bug will be deferred to a later release.