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

Bug: A problem which impairs or prevents the functions of the product.
New Feature: A new feature of the product, which has yet to be developed.
Story: A user story. Created by JIRA Software - do not edit or delete.
Task: A task that needs to be done.
Improvement: An improvement or enhancement to an existing feature or task.
Change Request
HR-Admin Support
IT-Support
Purchase: Track items that need to be bought. Created by JIRA Service Desk.
Change: For system upgrades or alterations. Created by JIRA Service Desk.
Fault: Track system outages or incidents. Created by JIRA Service Desk.
Access: For new system accounts or passwords. Created by JIRA Service Desk.
Information Security Incident: An information security incident is indicated by a single or a series of unwanted or unexpected information security events that have a significant probability of compromising business operations and threatening information security.Examples of information security events and incidents are: Loss of service, equipment or facilities System malfunctions or overloads Human errors Non-compliances with policies or guidelines Breaches of physical security arrangements Uncontrolled system changes Malfunctions of software or hardware Access Violations Password Reset in dropbox
Software Installation
IT Help: For general IT problems and questions. Created by JIRA Service Desk.
Finance Task Alocation
Enhancement: Enhancement feature
Incident: For system outages or incidents. Created by JIRA Service Desk.
Service Request: Created by JIRA Service Desk.
Problem: Track underlying causes of incidents. Created by JIRA Service Desk.
Story A
Epic: A big user story that needs to be broken down. Created by JIRA Software - do not edit or delete.

For Sub-Task Issues

Technical task
Sub-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.

Blocker: Blocks development and/or testing work, production could not run.
Critical: Preferred target - 2 to 8 hours , Business requires fast response to prevent negative impact to the firm eg: Virus threat, Partial disruption of activities (affecting up to 30% of operations), Unauthorized disclosure of confidential information.
Major: Crashes, loss of data, severe memory leak.
Minor: Minor loss of function, or other problem where easy workaround is present.
Trivial: Preferred target – 2 to 5 days ,Business is flexible with potential delay in response and there is no negative impact to the firm eg: Tailgating, Unclaimed Access cards etc.

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.
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.
Norway: This status is managed internally by JIRA Software
Sweden
Named (test): A story is given a name, but not planned to do yet
Scheduled (test): We have decided we will do this
Described (test): We have described what it will look like when this is done
Done (test): The developers have declared themselves done
Reviewed (test): Someone else has checked the work
Demonstrated (test): Included in a demo for the customer
Deployed (test): Deployed to users
Queued: Started, but not being worked on
Discarded (test): We won't do this after all
Backlog: This status is managed internally by JIRA Software
OnHold
Waiting for support: This was auto-generated by JIRA Service Desk during workflow import
Waiting for customer: This was auto-generated by JIRA Service Desk during workflow import
To Do
Done
Selected for Development
Waiting to Customer: This status is managed internally by JIRA Software
Declined: This was auto-generated by JIRA Service Desk during workflow import
Awaiting approval: This was auto-generated by JIRA Service Desk during workflow import
In review: This status is managed internally by JIRA Software
Deployed: This status is managed internally by JIRA Software
Accepted: This status is managed internally by JIRA Software
Ready for Verification: This status is managed internally by JIRA Software
Testing: This status is managed internally by JIRA Software
Awaiting implementation: This was auto-generated by JIRA Service Desk during workflow import
Wont Fix: This status is managed internally by JIRA Software
DEVELOPER COMPLETED: This status is managed internally by JIRA Software
QA In Progress: This status is managed internally by JIRA Software
Dev Completed: This status is managed internally by JIRA Software
QA Completed: This status is managed internally by JIRA Software
Ready For QA: This status is managed internally by JIRA Software
Deffered: This status is managed internally by JIRA Software
Acknowledged: This status is managed internally by JIRA Software
In Testing: This status is managed internally by JIRA Software
Development Done: This status is managed internally by JIRA Software
Testing in Progress: This status is managed internally by JIRA Software
Review: This status is managed internally by JIRA Software
In Test: This status is managed internally by JIRA Software
Moved: This status is managed internally by Jira Software
QA: This status is managed internally by Jira Software
Hold: This status is managed internally by Jira Software
To Do
In Progress
Done
To Do/Backlog
In Progress
Done
Dev-Complete
To Do
In Progress
Done
To Do
In Progress
Done
Dev Complete/QA
Prod Ready
UAT: 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.

Fixed: A fix for this issue is checked into the tree and tested.
Won't Fix: The problem described is an issue which will never be fixed.
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.
Done: GreenHopper Managed Resolution
Won't Do: This issue won't be actioned.
Declined: This issue was not approved.