Issue types, priority levels, and statuses
There are various symbols associated with issues. These describe metadata about the issue, such as what type of issue it is, how high of priority the issue is, where in the issue's lifecycle it currently sits, and how it may have been resolved.
Types of issues and their meanings
To sort what actions need to be taken on an issue, BTS uses 'types' as a way of filtering issues. The issue types are listed below in alphabetical order.
| Icon | Description |
|---|---|
 |
A bug is a problem which impairs or prevents the functions of the product. |
 |
A change request is an improvement or enhancement to an existing feature or task. |
 |
A feature request is a new feature of the product, which has yet to be developed. |
 |
A patch is a workaround that should be applied. |
 |
A support request provides answers to a technical support question and is only relevant for customer projects. |
 |
A task directs work that needs to be done. |
Priority levels and their meanings
An issue has a priority level that indicates its importance in the project. Knowing the specific meaning of these levels helps direct work in the flow appropriately.
| Icon | Description |
|---|---|
 |
P1 issues are the highest priority. All defects at this priority must be fixed before any public product is delivered. |
 |
P2 issues must be addressed before a final product is delivered. |
 |
P3 issues should be addressed before a final product is delivered. If the issue cannot be resolved before delivery, it should be prioritized for the next release. |
 |
P4 issues can be shipped with a final product. Opera is aware of these issues, and the number of them should be kept low, but the issue will not affect a large customer base. P4 issues should be reviewed before the next release. |
 |
P5 issues are the lowest priority. These issues are cosmetic and Opera can ship final products with any number of these defects. |
 |
Issues are unprioritized when they are new. If you notice an unprioritized issue, contact the reporter or set an appropriate priority level. |
Issue statuses and their meanings
Each issue has a status, which indicates where the issue currently is in its workflow, the lifecycle of the issue. You can read more about workflows in the understanding workflows section.
Statuses are grouped by color. Blue means that the issue is new. Yellow indicates that the issue is in-progress. And, green means the issue has been resolved.
Taking action on an issue moves that issue along the workflow, and automatically labels the issue with a new status. The most common statuses are listed below, alphabetically, with a note referring to the status' associated workflow. There are, at the time of writing this 47 statuses in BTS. Most are project-specific or related to quality assurance. If you have questions about a status that is not listed here, check with the project lead. You can find their contact information on the project's overview.
- Accepted
- The resolution has been accepted by the customer. This is associated with the following workflows: bug and patch, and change and feature request.
- Approved
- The feature or change request has been approved. This is associated with the change and feature request workflow.
- Confirmed
- The issue has been confirmed as a bug, and appropriate testcases have been created. This is associated with the bug and patch workflow.
- Examined
- The issue has been checked by front-line support, and is a valid issue. This is associated with the following workflows: bug and patch, and change and feature request.
- Inactive
- The issue has been untouched for a long period of time. This is associated with any workflow.
- New
- This is a newly reported issue. No action has been taken on it yet. This is associated with all workflows.
- Planned
- The task or response to the support request has been planned. This is associated with the task workflow.
- Resolved
- A resolution has been taken, and it is awaiting verification by the reporter. From here, issues are either reopened, or are closed. This is associated with the following workflows: bug and patch; change and feature request; task.
- Verified
- The resolution has been verified as being satisfactory.This is associated with the following workflows: bug and patch; change and feature request; and task.
- Completed
- An external task has been completed.
- Fixed
- A fix for the bug is checked into the tree and tested. The task has been completed, or a response to the support request has been sent.
- Implemented
- The request has been completed and put into action.
- Invalid
- The issue is not completely described, or is not a valid bug or request.
- Rejected
- The request will be rejected.
- Sitepatch
- The issue was fixed using site patching (e.g. browserjs).
- Unresolved
- The issue is still being worked.
- Won't fix
- The issue described is one that will never be fixed.
- Works for me
- At least 10 attempts to reproduce the issue failed. Must be able to demonstrate significant attempt.
Issue resolution
An issue can be resolved in many ways, only one of them being fixed. The defined resolutions are listed below in alphabetical order.