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.
Epic
Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down.
Story
Created by Jira Software - do not edit or delete. Issue type for a user story.
New Feature
A new feature of the product, which has yet to be developed.
Improvement
An improvement or enhancement to an existing feature or task.
Test
A new unit, integration or system test.
Wish
General wishlist item.
Task
A task that needs to be done.
New TLP
New TLP - Common Tasks
Blog - New Blog Request
Blogs - New Blog User Account Request
Blogs - Access to Existing Blog
New Bugzilla Project
SVN->GIT Mirroring
IT Help
For general IT problems and questions. Created by JIRA Service Desk.
Access
For new system accounts or passwords. Created by JIRA Service Desk.
Choose from below ...
Choose an issue type.
RTC
An RTC request
TCK Challenge
Challenges made against the Sun Compatibility Test Suite
Dependency upgrade
Upgrading a dependency to a newer version
Request
Question
A formal question. Initially added for the Legal JIRA.
Temp
Brainstorming
A place to record back and forth on notions not yet formed enough to make a 'New Feature' or 'Task'
Umbrella
An overarching type made of sub-tasks
Requirement
Comment
Planned Work
Assigned specifically to Contractors by the VP Infra or or other VP/ Board Member.
Outage
Pagerduty will use this to create tickets when an Incident occurs.
Office Hours
Issues designed to be discussed during Office Hours meetings.
Pending Review
Acknowledged but not planned work, or long range feature request in need of scoping and prioritization.
Board Vote
Technical Debt
Project
Which project does this relate to?
Volunteer
An issue suitable for a Volunteer
Proposal
GitBox Request
Dependency
Issue is dependent on ...
New JIRA Project
A request for a new JIRA project to be set up
Suitable Name Search
A search for a suitable name for an Apache product
Documentation
Documentation or Website
New Confluence Wiki
A request for a new Confluence Wiki to be set up
New Git Repo
Github Integration
SVN->GIT Migration
For Sub-Task Issues
Sub-task
The sub-task of the issue
Technical task
A technical task.
Director Vote

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
Urgent
This issue should block release until it is resolved, and trigger immediate release once resolved.
Critical
Crashes, loss of data, severe memory leak.
High
Major
Major loss of function.
Normal
Minor
Minor loss of function, or other problem where easy workaround is present.
Low
Trivial
Cosmetic problem like misspelt words or misaligned text.
P0
Outage blocking development and/or testing work; requires immediate and continuous attention
P1
Critical bug: data loss, total loss of function, or loss of testing signal due to test failures or flakiness
P2
Default priority. Will be triaged and planned according to community practices.
P3
Non-urgent bugs, features, and improvements
P4
Trivial items, spelling errors, etc.
Not a Priority

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 not closed can be reopened.
Blocked
The issue is open but work on it is temporarily suspended until further feedback is received determining its resolution.
Continued
The issue was on hold, and feedback was received indicating that further action are required towards its resolution.
Patch Available
A patch for this issue has been uploaded to JIRA by a contributor.
Patch Reviewed
A patch attached to this issue has been reviewed by another contributor.
Reviewable
Issue is to be reviewed before resolving/closing
Documentation Required
Documentation needs to be updated/created before resolving/closing the issue
Testcases Required
Further (unit and/or integration) test cases are required before resolving/closing the issue
Documentation/Testcases Required
Documentation and Test Cases must be created/updated before resolving/closing the issue
Waiting for user
Waiting for Infra
Testing
Patch is being tested, to be approved or rejected.
Unknown
Test requires a review to see if it is worth porting
Requires Porting
Test has been determined to be useful and worth the time porting
Not Applicable
Test not generally applicable or not worth the time to port
Ported
Done
In Review
To Do
Accepted
Pending Closed
Auto Closed
Ready to Commit
Awaiting Feedback
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
New
New Issue
Fixed
Fixed
Invalid
Invalid
FixedInBranch
Fixed In a Branch
Duplicate
Duplicate
Verified
Verified
WontFix
WontFix
UnderReview
Under Review
Started
Started
For Review
For Review
Idea
Abandoned
Under Discussion
Completed
In Implementation
on hold
This status is managed internally by JIRA Software
Triage Needed
Review In Progress
Changes Suggested
Requires Testing
Pull Request Available
Pull Request Merged
For Review - 2
Draft
Voting
Passed
Failed
Pending
Yes
No
Abstain
Needs Committer
This issue needs an additional review.
In Tests
Triaged
The issue has undergone preliminary assessments
Fix Released/Published
The issue has been released as part of a public release

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.
Invalid
The problem isn't valid and it can't be fixed.
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.
Later
Later
Not A Problem
The described issue is not actually a problem - it is as designed.
Implemented
As the name suggests
Done
Auto Closed
This issue was automatically closed
Pending Closed
REMIND
REMIND
Resolved
Resolved
Not A Bug
Not A Bug
Workaround
Workaround
Staged
Staged
Delivered
Delivered
Information Provided
Information Provided
Works for Me
Works for Me
Feedback Received
Feedback Received
Won't Do
Won't Do
Abandoned
Issues which have gone without any activity for an extended period of time