Jira - Local help - Jira

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

IT Help: An IT problem or question.
Service Request: A request that follows ITSM workflows.
Service Request with Approvals: A requests that may require approval.
Task: A small, distinct piece of work.
Bug: A problem or error.
Story: Created by Jira Agile - do not edit or delete. Issue type for a user story.
[System] Incident: For system outages or incidents. Created by Jira Service Management.
[System] Change: Created by Jira Service Management.
[System] Post-incident review: Document and share incident learning.
[System] Service request: A request that follows ITSM workflows.
[System] Service request with approvals: A request that follows ITSM workflows.
[System] Problem: Track underlying causes of incidents. Created by Jira Service Management.
Epic: A collection of related bugs, stories, and tasks.
Initiative: An initiative

For Sub-Task Issues

Sub-task
App Task

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.

Highest: This problem will block progress.
High: Serious problem that could block progress.
Medium: Has the potential to affect progress.
Low: Minor problem or easily worked around.
Lowest: Trivial problem with little or no impact on progress.

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.

Wont do
blockers
Testing
Ready to merge
Ready to prod
Reviews
Completed
Won't do
Review
Ready to integrate to frontend
Blocked
Reviews
to be done today 23 aug
Status updates
QA
FAILED THE REVIEW
Blocked
Done Wait. for Back-& Frontend
HotFix
PRIO 1
Paused
PRIO 2
IceBucket
review&merge
PRIO 1 NEW ITEMS
PRIO 3
TO BE REVIWED BY BUSINESS
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.
Building: Source code has been committed, and JIRA is waiting for the code to be built before moving to the next status.
Build Broken: The source code committed for this issue has possibly broken the build.
To Do
In Progress: This issue is being actively worked on at the moment by the assignee.
Done
Waiting for support: This was auto-generated by Jira Service Management during workflow import
Waiting for customer: This was auto-generated by Jira Service Management during workflow import
Done with Mock: This was auto-generated by Jira Service Management during workflow import
Cancelled: This was auto-generated by Jira Service Management during workflow import
Escalated: This was auto-generated by Jira Service Management during workflow import
Declined: This was auto-generated by Jira Service Management during workflow import
Waiting for approval / QA: Waiting to be approved by Tech Lead or CTO
Work in progress: This was auto-generated by Jira Service Management during workflow import
Done
To Do
In Progress: This issue is being actively worked on at the moment by the assignee.
Done
To Do
In Progress: This issue is being actively worked on at the moment by the assignee.
Done
To Do
In Progress: This issue is being actively worked on at the moment by the assignee.
Done
To Do
In Progress: This issue is being actively worked on at the moment by the assignee.
Done
To Do
In Progress: This issue is being actively worked on at the moment by the assignee.
Done
To Do
In Progress: This issue is being actively worked on at the moment by the assignee.
Done
To Do
In Progress: This issue is being actively worked on at the moment by the assignee.
Done
To Do
In Progress: This issue is being actively worked on at the moment by the assignee.
Done
To Do
Blocked: If you are blocked by something, put the ticket in this status and mention why.
To Do
In Progress: This issue is being actively worked on at the moment by the assignee.
Done
To Do
In Progress: This issue is being actively worked on at the moment by the assignee.
Done
To Do
In Progress: This issue is being actively worked on at the moment by the assignee.
Done
TO-DO
ONGOING
Done
Pending: This was auto-generated by Jira Service Management during workflow import
Waiting for approval: This was auto-generated by Jira Service Management during workflow import
Review: This was auto-generated by Jira Service Management during workflow import
Implementing: This was auto-generated by Jira Service Management during workflow import
Planning: This was auto-generated by Jira Service Management during workflow import
Authorize: This was auto-generated by Jira Service Management during workflow import
Completed: This was auto-generated by Jira Service Management during workflow import
Failed: This was auto-generated by Jira Service Management during workflow import
Awaiting implementation: This was auto-generated by Jira Service Management during workflow import
Under investigation: This was auto-generated by Jira Service Management during workflow import
Under review: This was auto-generated by Jira Service Management during workflow import
Awaiting approval: This was auto-generated by Jira Service Management during workflow import
Draft: This was auto-generated by Jira Service Management during workflow import
Published: This was auto-generated by Jira Service Management during workflow import
Awaiting CAB Approval
Waiting For Reporter
CAB Rejected
CAB Approved
Pending Review
CAB Deferred
Cancelled
QA: This status is managed internally by Jira Software
Failed the QA: This status is managed internally by Jira Software
Done Wait. for Back-& Frontend: This status is managed internally by Jira Software
Review & Merge: This status is managed internally by Jira Software
paused: This status is managed internally by Jira Software

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.

Done: Work has been completed on this issue.
Won't Do: This issue won't be actioned.
Duplicate: The problem is a duplicate of an existing issue.
Declined: This issue was not approved.
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 behaviour would occur. If more information appears later, please reopen the issue.