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
Priority Levels
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.
-
Open in Assessment
- Ticket being reviewed for impact
-
Open in Resolution
- Issue has been assigned but not worked.
-
Resolution Pending
- Actively working towards implementing code changes, License Request and/or Final Analysis
-
Open in Verification
- In Verification waiting to be acted upon.
-
In Progress - Verification
- Issue being verified that fix was applied correctly
-
Frozen
- Issues has been committed to a fix version
-
Proposed
- Issue is slotted for the fix version
-
Evaluation
-
Resolution
-
Verification
-
Estimation
-
Under Analysis
- Determine how the issue should be handled.
-
In Development
- The issue is being addressed by the development team
-
On Hold
- The issue cannot be worked on. Waiting. See Reason Code and Reason Description.
-
Assigned
-
Monitor
-
Review
-
Sustaining
-
Work-In-Progress
-
In Prod Develop
- in TIERONE TNP Product group
-
In 3rd Party
- In 3rd party vendor support
-
in Prof Services
- in TIERONE Managed services group
-
Work in Progress
- Analysis of request complete; work to complete resolution
-
Under Investigation
- Issue is being investigated by the development team
-
Rework
- This incident was set to resolved, but the resolution was deemed incorrect.
-
Scheduling
- Plan Patch/Release or configuration installation
-
Fix Pending
- A temporary fix or workaround is available; permanent fix being worked on
-
Fix Scheduled
- Release with which fix will be applied has been determined
-
In Prod Mgmt
- In Prod Mgmt
-
Approved
-
Merge
- Ticket requires to be merged.
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.
- Resolve
- This issue will be or has been resolved.
- Deferred
- The problem described is an issue which will not be addressed at this time.
- Duplicate
- The problem is a duplicate of an existing issue.
- Incomplete
- The problem is not completely described.
- 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.
- No Action Required
- Issue was added in error.
|