|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
- the issue
- a summary
- a description of the issue
- the project which the issue belongs to
within a project which are associated with this issue
of the project which are affected by this issue
- versions of the project which will resolve
- 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
- a comment trail added by users
- if the issue is resolved - the resolution
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
A problem which impairs or prevents the functions
of the product.
An improvement or enhancement to an existing
feature or task.
A new feature of the product, which has yet
to be developed.
TC Charter Submission
A task that needs to be done.
For Sub-Task Issues
The sub-task of the issue
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.
Blocks development and/or testing work, production
could not run.
Crashes, loss of data, severe memory leak.
Major loss of function.
Minor loss of function, or other problem
where easy workaround is present.
Cosmetic problem like misspelt words or misaligned
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.
The issue is open and ready for the assignee
to start work on it.
This issue is being actively worked on at
the moment by the assignee.
This issue was once resolved, but the resolution
was deemed incorrect. From here issues are either marked assigned or resolved.
A resolution has been taken, and it is awaiting
verification by reporter. From here issues are either reopened, or are
The issue is considered finished, the resolution
is correct. Issues which are closed can be reopened.
QC of document(s)
upload/testing of files at docs.oasis-open.org
announcement to members or TC
ballot results announce
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.
A fix for this issue is checked into the
tree and tested.
The problem described is an issue which will
never be fixed.
The problem is a duplicate of an existing
The problem is not completely described.
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.