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
JIRA service request
JIRA service request
Virtual machine service request
VTIGER service request
Emergency service request
Workstation service request
Workstation service request
Office hardware service
Office hardware service
Forum service request
Forum service request
Website service request
Website service request
Security permissions request
Security permissions request
Source code service request
Confluence service request
Confluence service request
Network upgrade request
Network upgrade request
Software upgrade request
Software upgrade request
Hardware upgrade request
Hardware upgrade request
Material resource request
Material resource request
Idea
Idea
Elaboration
Elaboration
Product Defect
All questions are related to unexpected product behaviour, crashes and etc.
Integration
Turn-Key
Termination of employment
Delete rights for existing employees (on-hold)
New rights for existing employees (on-hold)
New employee
Regular task
New task
Planned maintenance
Upgrade Task
Questions are related to upgrade task from one version to another and migration tasks.
Change access rights
Access right review
Problem
Track underlying causes of incidents. Created by Jira Service Desk.
NCR
Nonconformity
OFI
Opportunity for Improvement
Request For Quotation
Request For Quotation
Request For Proposal
Request For Proposal
Request For Information
Request For Information
Defect (Refactoring)
Defect (Refactoring)
Documentation task
Documentation task
Patch request
Patch request
Problem report
Problem report
Incident report
Incident report
Exam
Zabbix training Exam
Non-functional test
Non-functional test
Auto test
Auto test
Manual test
Manual test
Course
Zabbix training course
Architecture design (PoC)
Architecture design (PoC)
Product delivery
Product delivery
Defect (Non-functional)
A defect which impacts non-functions of the product
Defect (Security)
Discovered security vulnerabilities in Zabbix
Defect (Functional)
A defect which impacts or prevents functions of the product
Risk
ISMS Risk
REM
ISMS REM
Integrations
Questions related to Product Integrations
Create template
Create template
Performance Problem
Questions are related to product stability issues.
Product Usage
All questions are related to product configuration, planning and usage.
Improvement Request
All modifications or improvements to already existing product features.
Feature Request
All new features requests. A customer should use the type to request features which are not present in the product.
Marketing Support
Marketing Support
Update module
Create module
Update template
Update template
Estimation
Estimation
Project
Project
Improvement
Improvement
New Feature
New Feature
On Hold
Template
Issue Type for Templates
Corrective action (CA)
New 3rd party access rights
Epic
Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down.
Bug
A problem which impairs or prevents the functions of the product.
New Feature Request
A new feature request of the product, which has yet to be developed.
Story
Created by Jira Software - do not edit or delete. Issue type for a user story.
Task
A task that needs to be done.
Change Request
An Change Request or enhancement Improvement to an existing feature or task.
Service Request
Created by Jira Service Desk.
IT Help
For general IT problems and questions. Created by Jira Service Desk.
Support
For customer support issues. Created by JIRA Service Desk.
Service Request with Approvals
For requests that require approval. Created by Jira Service Desk
For Sub-Task Issues
Manual test (Sub-task)
Manual test
Change Request (Sub-task)
Change Request
Specification change (Sub-task)
Specification change
Auto test (Sub-task)
Auto test
Sub-Template
Sub-Issue Type for Templates
Non-functional test (Sub-task)
Non-functional test
Documentation (Sub-task)
Documentation
Work Item
Work Item
Sub-task
The sub-task of the issue
Technical task
Created by JIRA Agile - do not edit or delete. Issue type for a technical 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
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.
High
Serious problem that could block progress.
Medium
Has the protential to affect progress.
Low
Minor problems or easily worked around.

Statuses

Status Categories

Helps identify where an issue is in its lifecycle.
Issues move from To Do to In Progress when work starts on them, and later move to Done when all work is complete.

Done

Represents anything for which work has been completed

In Progress

Represents anything in the process of being worked on

No Category

A category is yet to be set for this status

To Do

Represents anything new

Issue 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.
Confirmed
The issue is confirmed by Zabbix Team
Need info
Additional information is required
Merging
Solution for the issue has been successfully tested. It is ready for integration.
Done
A fix is integrated into Zabbix base code.
Needs documenting
A fix needs to be documented
Doc. sign-off
A fix is documented and needs to be reviewed
READY TO DEVELOP
The issue must be implemented
IN MANUAL TESTING
Manual testing
IN DOCUMENTING
In specification
Specification in progress
IN QA
QA testing
Canceled
Elaborating
Elaborating
Needs specification
Needs specification
Spec. sign-off
Specification sign off
Ready for QA
Ready for QA
Backloged
Backloged
QA Failed
Manual Test Failed
Fix for QA
Fix for Manual Testing
Blocked
Review QA fix
Postponed
Wait Response
Development Request
New
Roadmap Decision
The request is forwarded to Sales team.
To Do
Solution Offered
Zabbix On It
Waiting for Customer
QA Fix ready
QA Fix ready
Require Auto Test
Require Auto Test
Covering with Auto Tests
Covering with Auto Tests
Validating
Require approval
In Review
Looking for sponsor
Looking for sponsor
Proposed
Proposed
Declined
Declined
Roadmap Triage
Roadmap Triage
Requirements Breakdown
Requirements Breakdown
Defining Acceptance
Defining Acceptance
Technical Risks Validation
Technical Risks Validation
Zabbix Sign-off
Zabbix Sign-off
Sponsor Sign-off
Sponsor Sign-off
Estimation
Estimation
Planing
Planing
On Hold
On Hold
Ready for invoice
Ready for invoice
Invoiced
Invoiced
Order Suspended
Order Suspended
Executing
Executing
Delivered
Delivered
Accepted
Accepted
Feature Demo
Feature Demo
UX/UI Design
UX/UI Design
Approved
The issue is approved to start work on it.
Ready for Blog-post
Writing Blog-post
Sign-off Blog-post
Waiting for support
This was auto-generated by JIRA Service Desk during workflow import
Pending
This was auto-generated by JIRA Service Desk during workflow import
Escalated
This was auto-generated by JIRA Service Desk during workflow import
Work in progress
This was auto-generated by JIRA Service Desk during workflow import
Ready for Review
Stop Review
Waiting for approval
Waiting for Hardware
Hardware issued
Handover done
User account is blocked
Clarification is needed
Access is accepted
Access is declined
Access is provided
No changes are needed
Access should be changed
Sign off by Support
Usability Check
Draft
Published
Archived
NDA
Legal validation
Hardware returned
Review Failed
QA Passed
Evaluation

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.
Unsupported version
Unsupported version
Workaround proposed
Workaround proposed
Commercial support required
Commercial support required
Change request declined
Change request declined
Done
Won't Do
This issue won't be actioned.
Declined
This issue was not approved.
Known Error
The problem has a documented root cause and a workaround.
Hardware failure
Software failure
False Positive