This page describes the various fields that you see on a bug.

STATUS
The Status field indicates the current state of a bug. Only certain status transitions are allowed.
Open Bugs
NEW
This bug report has recently been entered into Red Hat Bugzilla, and must be processed. Bug reports in this state may be moved to ASSIGNED or CLOSED They can also be reassigned to another engineer or component.
ASSIGNED
This bug report is being worked on by the Assigned Engineer. Use of this state is optional.
POST
This bug report has a fix that has been posted for review, either upstream or internally, by the Assigned Engineer. Use of this state is optional. Some teams, such as kernel and virtualization, use it.
MODIFIED
This bug report has been fixed, unit tested and checked into source control by the Assigned Engineer.
ON_DEV
This bug report is being worked on by the Assigned Engineer. Use of this state is optional.
ON_QA
This bug fix is available for the Assigned Quality Engineer to test. If not using the Errata Tool, typically moved to ON_QA by RCM when the bug fix has been incorporated into a build which is available to be tested. If using the Errata Tool, moved to ON_QA automatically when the bug number is added to the erratum’s bug list, and a build is available to be tested. Test cases or plans are written and available.
VERIFIED
This bug fix has successfully finished testing by the Assigned Quality Engineer. If not using the Errata Tool,bug reports may move to CLOSED once verified in a build.
RELEASE_PENDING
This bug fix is being prepared for delivery to customers by the Assigned Release Configuration Management Engineer. The most likely next state is CLOSED. If using the Errata Tool, this state change happens automatically when the advisory is shipped. It is also possible that the bug report may transition back to ASSIGNED if a problem has been found.
Closed Bugs
CLOSED
This bug fix has been resolved by the Assigned Engineer. The CLOSED state includes the resolution field which describes why a bug report is closed. See Resolution descriptions. If the CLOSED resolution ERRATA is set, the bug report cannot be reopened. Instead, enter a new bug report for a new problem.

RESOLUTION

The Resolution field indicates what happened to this bug.
CURRENTRELEASE
The problem described has been fixed in the current supported release.
DUPLICATE
The problem is a duplicate of an existing bug report. Marking a bug report duplicate requires the bug number of the duplicate bug report.
ERRATA
The problem described has been fixed and is available as an update from our support web site.
NOTABUG
The problem described is not a bug. An explanation of why this resolution has been chosen should be supplied as a comment.
WONTFIX
The problem described is a bug report which will not be fixed. An example of why this might be true is due to significant divergence from upstream. An explanation of why this resolution has been chosen should be supplied as a comment.
CANTFIX
The problem described is a bug report which cannot be fixed. It may be for a component which we do not support, or a bug report that has not received a reply after requesting "needinfo" of someone for a while. If possible, use more common resolutions such as WONTFIX or NOTABUG. If you must choose this resolution, provide an explanation of why this resolution has been chosen in a comment.
DEFERRED
The problem described is a bug which will be fixed in the next supported release, but which is not planned to be released in the release against which the bug was filed. If a release flag is being used on this bug report, it is preferred to move it to the next release flag instead of setting the Status field to CLOSED and the Resolution field to DEFERRED. If you must choose this resolution, provide an explanation of why this resolution has been chosen in a comment.
INSUFFICIENT_DATA
The problem description is insufficient for the assignee to work on the bug report. This may be due to a lack of clear requirements or insufficient information to reproduce the bug. Before using this resolution, please use the needinfo flag to request more information and allow a reasonable time for the information to be provided. If you must choose this resolution, provide an explanation of why this resolution has been chosen in a comment.
NEXTRELEASE
The problem described has been fixed in the next supported release of the product, and is not planned to be fixed in the release against which the bug was filed. If a release flag is being used on this bug report, it is preferred to move it to the next release flag instead of setting the Status field to CLOSED and the Resolution field to NEXTRELEASE. If you must choose this resolution, provide an explanation of why this resolution has been chosen in a comment.
RAWHIDE
The problem described has been fixed in the latest development release of our product obtainable from our ftp site. This resolution should not be used for Red Hat Enterprise Linux bugs.
UPSTREAM
The problem described has been filed in an upstream bug tracker or reported to the upstream mailing list. This typically includes almost all feature requests and enhancements, and most bugs that we don't consider release showstoppers. (Moving bugs upstream typically increases the chance that someone will have time to look at it, and often the upstream developer or bug owner even works at Red Hat.

Moving bugs upstream simply allows us to keep everything in one place, and work better with open source community developers outside of Red Hat. We only keep bugs open on redhat.com to track our immediate short-term items, or issues with our patches and/or packaging, or because the upstream package in question has poor bug tracking.

The main focus of development for most packages is the upstream community, even when Red Hat is a big contributor to the community.) Some upstream bug trackers include http://bugzilla.gnome.org, http://bugs.kde.org, and http://bugzilla.mozilla.org. This resolution should not be used for Red Hat Enterprise Linux bugs.
WORKSFORME
The problem described is not a bug. It is preferred that resolution NOTABUG be used if problem has been determined to not be a bug, or use the needinfo flag if more information is needed. If you must choose this resolution (in Fedora, for example), provide an explanation of why this resolution has been chosen in a comment. This resolution should not be used for Red Hat Enterprise Linux bugs.
EOL
The release is no longer supported, a Fedora specific resolution. See the Fedora wiki
MIGRATED
This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored. Bugs with this resolution will have an external tracker link to the new site.

If you have permission to view the external tracker link then the link will be directly to the new issue. If you lack permission then the link will be to the root of the new site.

COMPLETED
This bug is a workflow task and it has been completed.

Other Fields

Alias
A short, unique name assigned to a bug in order to assist with looking it up and referring to it in other places in Bugzilla.
Assignee
The person in charge of resolving the bug.
Blocks
This bug must be resolved before the bugs listed in this field can be resolved.
Bug ID
The numeric id of a bug, unique within this entire installation of Bugzilla.
Category
What kind of bug is this?
CC
Users who may not have a direct role to play on this bug, but who are interested in its progress.
Changed
When this bug was last updated.
Classification
Bugs are categorised into Classifications, Products and Components. classifications is the top-level categorisation.
Clone Of
The bug listed here was the bug cloned to create this bug
Cloudforms Team
This records what team is working on the bug.
Comment
Bugs have comments added to them by Bugzilla users. You can search for some text in those comments.
Comment is private
A custom Unknown Type field in this installation of Bugzilla.
Component
Components are second-level categories; each belongs to a particular Product. Select a Product to narrow down this list.
Content
This is a field available in searches that does a Google-like 'full-text' search on the Summary and Comment fields.
Creation date
When the bug was filed.
CRM
Poor alternative to External Trackers
Deadline
The date that this bug must be resolved by, entered in YYYY-MM-DD format.
Dependent Products
Dependent Products allows you to track when a bug in one product has an impact on other products.

e.g. The version of Java shipped in an operating system may impact middlewar in another product.

Depends On
The bugs listed here must be resolved before this bug can be resolved.
Doc Text
This field is the basis of the errata or release note for this bug. It can also be used for change logs.

The Technical Note template, known as CCFR, is as follows:

Cause
What actions or circumstances cause this bug to present.
Consequence
What happens when the bug presents.
Fix
What was done to fix the bug.
Result
What now happens when the actions or circumstances above occur.
Note: this is not the same as the bug doesn’t present anymore.

When documenting a Known Issue, use the CCWR variation as follows:

Cause
What actions or circumstances cause the bug to present (if known).
Note: if the cause is not known or is not fully diagnosed,
current hypotheses or theories should be noted.
Consequence
What happens when the bug presents.
Workaround
What actions, if any, reduce the bug’s effects or prevent it from presenting entirely.
Result
If the bug’s effect is only reduced, what consequences still flow;
if the bug is prevented, what restrictions does the workaround impose.

When documenting a new feature (e.g. an RFE), use the FRR variation as follows:

Feature
Describe the new feature that has been added.
Reason
Give the reason why this feature was needed.
Result
Describe the functionality, work-flow, or appearance etc. that has changed, or is now available, due to this new feature.
Doc Type
This field is a pull-down used to indicate the type of documentation to appear in the next field "Doc Text". Depending on the value chosen, the template in the "Doc Text" field will change accordingly.
Docs Contact
The person responsible for documenting once the bug has been resolved.
Documentation
Inscrutable drop down.
Embargoed
This issue is currently under an embargo.
Environment
This field is used for unformatted text that helps to further describe the bug report.
Extra Private Groups
A custom Unknown Type field in this installation of Bugzilla.
Fixed In Version
The full package version. PGM uses to check if brew build is in errata tool.
Flag Requestee
A custom Unknown Type field in this installation of Bugzilla.
Flag Setter
A custom Unknown Type field in this installation of Bugzilla.
Flags
A custom Unknown Type field in this installation of Bugzilla.
Hardware
The hardware platform the bug was observed on. Note: When searching, selecting the option "All" only finds bugs whose value for this field is literally the word "All".
A custom Integer field in this installation of Bugzilla.
Importance
The importance of a bug is described as the combination of its Priority and Severity.
Keywords
You can add keywords from a defined list to bugs, in order to easily identify and group them.
Last Closed
When this bug was last marked as closed. Used for statistical purposes.
Link ID
A custom Free Text field in this installation of Bugzilla.
Link Last Updated
A custom Free Text field in this installation of Bugzilla.
Link Priority
A custom Free Text field in this installation of Bugzilla.
Link Status
A custom Unknown Type field in this installation of Bugzilla.
Link Summary
A custom Free Text field in this installation of Bugzilla.
Link System Description
A custom Unknown Type field in this installation of Bugzilla.
Link System URL
A custom Unknown Type field in this installation of Bugzilla.
Locked
A bug that has been locked can only be updated by users with 'editbugs' rights on the bug's product.
Mount Type
How a disk is mounted
Number of Comments
A custom Unknown Type field in this installation of Bugzilla.
OS
The operating system the bug was observed on. Note: When searching, selecting the option "All" only finds bugs whose value for this field is literally the word "All".
oVirt Team
When opening bugs or RFEs on oVirt, if you don't set the oVirt team in the bug, these bugs go through some initial scrubbing mechanism, to determine which vertical is responsible for them.

However, in most cases the one opening the bug should be able to know what team it is related to. In some cases the issues are in between verticals, but in such case they can be set to one, and worst case they will be moved to another vertical, if needed.

The main values are:

  • Network - network issues either originated by the host, or the engine.
  • Storage - storage related issues, either originated by the host, or the engine.
  • Spice - spice/virt-viewer related issues.
  • Infra:
    • Authentication Issues.
    • General DB issues (not ones related to specific vertical flow).
    • Host monitoring/communication issues, host statuses, etc.
    • Host deployment/upgrade issues.
    • Certificate issues.
    • engine-config issues.
    • engine-notifier issues.
    • Fencing issues.
    • Scale issues.
    • Satellite/Foreman integration issues.
    • General REST-API issues (not ones related to specific vertical flow).
    • Python SDK, Java SDK and CLI issues.
    • IOPROCESS / python-pthreading / python-cpopen issues.
  • Reports - Reports engine issues.
  • Metrics:
    • Data warehouse (DWH) issues.
    • Metrics store issues.
    • Alerting framework issues.
    • Metrics visualizations issues.
  • SLA:
    • MoM.
    • Engine-related SLA issues (CPU / network / storage QOS).
    • Scheduling and load balancing issues.
    • Placement related issues.
    • CPU pinning.
    • NUMA.
    • Affinity.
    • hosted engine HA issues.
    • HA VMs issues.
    • Quota.
    • Optimizer.
  • Node:
    • ovirt-node issues.
    • oVirt appliance.
  • Virt:
    • VM issues.
    • Emulated machine errors.
    • VM console issues (VNC, SPICE, serial console).
    • templates / instance-types issues.
    • VM import/export, conversion via virt-v2v integration.
    • VM life-cycle issues.
    • general ovirt-guest-agent issues.
    • VM Pools.
  • Integration:
    • engine-setup / upgrade / cleanup issues (not ones related ot other vertical rfes / flows).
    • engine-backup / restore issues.
    • iso/image-uploader issues.
    • log collector issues.
    • hosted engine setup / upgrade issues (not ones related ot other vertical rfes / flows).
    • windows guest agent install/update issues (not virtio / spice / guest agent issues).
    • DWH & Reporting setup / upgrade / cleanup issues.
    • ovirt-live issues.
    • ovirt releng issues (unless releng should be used for upstream too).
    • debian packaging issues.
    • CentOS Virt SIG packaging issues.
  • UX:
    • General UX issues (not ones related to specific vertical flow).
    • UI Plugins.
  • i18n - translation issues (i.e. issues that require a translation update, not an English-text update).
  • Gluster - gluster issues.
  • Docs - documentation issues.
  • Rel-Eng - Anything related to product release engineering (tagging / Brew / etc).
  • Sub-Eng - anything related to Red Hat support plugin.
  • External - Anything that depends on another team not covered in the list above.
Personal Tags
Unlike Keywords which are global and visible by all users, Personal Tags are personal and can only be viewed and edited by their author. Editing them won't send any notification to other users. Use them to tag and keep track of bugs.
Pool
The Agile pool this bug is assigned to. See Agile Docs
Pool ID
The id of the Agile pool this bug is assigned to.
Pool Order
The order of this bug in it's Agile pool.
Pool team
A custom Unknown Type field in this installation of Bugzilla.
Priority

This field is a pull-down of the internal weighting of the bug report's importance and can have the following values:

urgent
extremely important
high
very important
medium
average importance
low
not very important
unspecified
importance not specified
Product
Bugs are categorised into Products and Components. Select a Classification to narrow down this list.
QA Contact
The person responsible for confirming this bug if it is unconfirmed, and for verifying the fix once the bug has been resolved.
Regression
What kind of regression is this?
Reporter
The person who filed this bug.
RHEL 7.3 requirements from Atomic Host
Poor alternative to External Trackers.
Severity
This field is a pull-down of the external weighting of the bug report's importance and can have the following values:
urgent
catastrophic issues which severely impact the mission-critical operations of an organization. This may mean that the operational servers, development systems or customer applications are down or not functioning and no procedural workaround exists.
high
high-impact issues in which the customer's operation is disrupted, but there is some capacity to produce.
medium
partial non-critical functionality loss, or issues which impair some operations but allow the customer to perform their critical tasks. This may be a minor issue with limited loss or no loss of functionality and limited impact to the customer's functionality.
low
general usage questions, recommendations for product enhancement, or development work.
unspecified
importance not specified
Story Points
A poor alternative to Original Estimate.
Sub Component
Some components have sub components in order to help bug triaging. A sub component has its own default assignee, qa and docs contact.
Summary
The bug summary is a short sentence which succinctly describes what the bug is about.
Target Milestone
The Target Milestone field is used to define when the engineer the bug is assigned to expects to fix it.
Target Release
The Target Release field is used to define when the bug is expected to be fixed.
Target Upstream Version
Target upstream version where the bug fix or feature is planned to be merged. If this is a kernel bug, please use the Upstream Kernel Target field instead.
Type
Keywords in a custom field.
URL
Bugs can have a URL associated with them - for example, a pointer to a web site where the problem is seen.
Verified Versions
A way to store what branch a bug is fixed in without making it a useful link like an External Tracker would.
Version
The version field defines the version of the software the bug was found in.
Votes
Some bugs can be voted for, and you can limit your search to bugs with more than a certain number of votes.
Whiteboard
Each bug has a free-form single line text entry box for adding tags and status information.