Name Description Open Bugs Total Bugs
ABIAssurance Bugs with "ABIAssurance" Keyword are used for tasks related to symbol categorization for backward compatibility. Search 499
AcceptanceCriteriaApproved An Acceptance Criteria review by QE, approved Acceptance Criteria and then QE design test cases depending on these approved Acceptance Criteria. Search 91
AcceptanceCriteriaNeeded An Acceptance Criteria is needed to make sure QE really know how to design test cases for it and how to test it. Search 9
AcceptanceCriteriaProvided An Acceptance Criteria has been provided by the Developers, assignee or contributor. Search 91
AcceptanceCriteriaRejected An Acceptance Criteria reveiw by QE, reject Acceptance Criteria. Search 10
Automation filtering bugs which were found by automatic testing Search 3383
AutomationBackLog We need to write/implement an automatic test for this use case/bug. Search 781
AutomationBlocker AutomationBlocker Search 2486
AutomationTriaged AutomationTriaged Search 2486
AutoVerified This bug has been verified by an automated test. QA is still responsible for setting the status to VERIFIED Search 1470
BetaBlocker This bug prevents delivery of beta software Search 136
Branch This keyword is used to identify packages that will require a branch from RHEL 7.4 User Space for Pegas 1.0. Search 38
Bugfix kernel/platform teams decides to use "Bugfix" to identify a bug that is fixing a real issue and possibly has a reproducer. Search 2643
BuildBlocker BuildBlocker Search 95
CodeChange A problem discovered in the code directly, does not require QA. Search 1204
CommonBugs Bugs with "CommonBugs" Keyword indicate that a bug should be documented on the Common Bugs page for the affected release(s) of Fedora. Add it to any moderately visible bug that is likely to be encountered by a reasonably large group of users. Search 862
CustomerScenariosInitiative A bug with this keyword was found as a result of use cases originating from the Customer Scenarios Initiative. It should be prioritized because it has been shown to have a significant negative impact on the customer experience. Search 195
DeliveryBlocker Used to identify bugs that specifically inhibit the ability to deploy to OpenShift Online on an established once-per-sprint basis Search 101
Desktop Bugs with this keyword identifies desktop applications with lost of core functionalities such as unable to start application successfully, application behaving strangely during normal usage and printing. They will be closely monitored to ensure that the bugs are verified before the next stable Fedora distribution becomes available. Search 3057
DevelBlocker This bug prevents a dependent feature or bug fix from being developed. Search 85
DevPreview Development Preview is planned for this package. Search 27
Documentation Bugs with the "Documentation" keyword are items to improve the documentation of a component. This could include errors in print, on-line help or man pages. Search 33503
EasyFix Marks bugs that are trivial easy-to-understand fixes that anyone could implement. For example fix URL or dependencies in spec file. Search 9094
EC2 Indicates a bug that is specific to Amazon EC2 images Search 118
Embedded A bug that is specific to embedded systems. Search 17
Epic An Epic is a large story that may act as a collection of bugs. Search 11
External External Search 247
Extras Issues released via "Extras" RHN channel. Search 5202
FastFix By "FastFix" keyword can be marked a bug matching following conditions: - fix is low risk - easy to test (clear reproducer) - easy to fix / implement Deadline for fastfix bug fix/implementation is mid-development phase. Please see details in minor release schedule. FastFix could added to open errata advisory also later in the cycle if approved for inclusion as any other bug fix. Search 711
FeatureBackport Add this keyword if this issue refers to a feature you would like to see backported to this Release. Search 849
Field for any bugs, RFEs coming from Field guys Search 14
FieldEngineering Bugs which have been identified via a Field Engineering program. Search 276
FutureFeature Add this keyword if this issue refers to a feature you would like to see in a future release of a Red Hat product. Search 217072
GraphicArt This bug is blocking on decisions or work from the graphic art department and can't be taken further by engineering alone. Search 37
GSS-NFV-Escalation NFV related bugzilla's escalated for review by DFG NFV Search 35
GSSTriaged For use during GSS feature review process. Search 60
HardwareEnablement Bugs with the "HardwareEnablement" keyword are items to implement support for a specific hardware component. Search 2351
HwCertBlocker To mark/highlight Bugzilla's typically in the Hardware Certification Program product that are currently or will in the future block certifications for which no known work around exists. Search 192
i18n Bugs with the "i18n" keyword are items to improve the internationalization of a component. This could include adding translations, changing code to be translatable, or changing code to be more translation friendly. Search 5504
Improvement An improvement or enhancement to an existing feature or task. Search 2378
ImprovesTestability Fixing a bug with this keyword will improve the ability to test the component. Search 14
InstallerIntegration efforts to track OpenStack RFEs that directly pertain to exposing features in the deployment tooling Search 115
ManPageChange Bugs with "ManPageChange" keyword will be addressed by changing existing or adding a new man page in the package it is reported against. Bug may be addressed in man-pages-overrides package if this package is available for the product. Search 1167
ManyUsersImpacted This bug should be prioritised because it impacts many users. Search 15
MigratedToJIRA This bug has been migrated to JIRA at https://issues.redhat.com/. Please follow the link provided for any further updates to it. Search 10306
MoveUpstream Bugs with this keyword are slated to be filed in the upstream bug tracker or reported to the upstream mailing list, then closed UPSTREAM on the Red Hat level. This typically includes almost all feature requests and enhancements, and most bugs that we don't consider release showstoppers. (Moving a bug 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 things 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 TODO items, or issues with our patches/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.) If a bug has this keyword, feel free to go ahead and move it upstream, add a link to the upstream report in our report, and then close the bug. Or we typically do this ourselves in batches. Search 944
NeedsTestCase This bug needs a test case to be created. Search 554
NoDocsQEReview The Quality Engineering team does not need to check the documentation on this bug. Search 1423
OnlineDedicated Bugs targeting the OpenShift Online Dedicated clusters. Search 95
OnlinePro Bugs targeting the OpenShift Online Pro tier. Search 431
OnlineStarter Bugs targeting the OpenShift Online Starter cluster Search 296
OpsBlocker Indicates this bug is blocking operational use of the product. Search 270
OracleCert Bugs with the "OracleCert" keyword are issues found during an Oracle Certification effort on Red Hat products. Search 10
OSE41z_next Manage OpenShift 41 maintenance releases. Search 45
OtherQA Bugs with the "OtherQA" keyword will be tested by parties other than Red Hat, Inc. Search 21982
Patch Bugs with this keyword have a patch attached; the patch needs reviewed for potential inclusion. Search 20614
Performance Bugs impacting the runtime performance Search 1570
PrioBumpField This keyword is added to bugs to note that the field would like to see the bug addressed sooner than later. Search 464
PrioBumpGSS This keyword is added to bugs to note that GSS would like to see the bug addressed sooner than later. Search 1058
PrioBumpPM This keyword is added to bugs to note that Product Management would like to see the bug addressed sooner than later. Search 340
PrioBumpQA This keyword is added to bugs to note that QE would like to see the bug addressed sooner than later. Search 304
PromotionBlocker Bugs with this keyword have a technical issue that prevents new code from being considered as part of the next supported release. Search 2
QA-Closed This keyword to be used when moving bugs from like NEW|ASSIGNED -> CLOSED. This is a way for QA to ensure that the bugs are closed appropriately. Search 612
Question Migrated Fogbugz questions Search 87
Rebase Indicates that this bug is a request to rebase a component to a newer upstream version. Search 63906
Regression Bugs with the "Regression" keyword are items where a recent change has introduced this bug. Search 37888
ReleaseNotes Keyword for tracking documentation of Release Notes. Search 291
Reopened Bug has been previously REOPENED from a CLOSED state. Search 65639
Reproducer Bugs with this keyword include a comment inline and/or an attached script or code that reproduces the issue. Search 1914
RevisionTracker Bugs with this keyword are used to track those revisions that need tracking. Search 1588
RFE Request For Enhancement Search 2673
RHELNAK Used to indicate a RHEL bug has been naked by the bugbot. Search 661
Scale This bug has a significant impact on large scale deployments. Search 71
screened Keyword screened for now is internally used by the 389 team for triaging bugs Search 229
ScreenshotChange Fixing this bug would break existing screenshots. i.e. fix the bug before docs freeze. Search 31
Security Bugs with the "Security" keyword are those that relate to a security vulnerability with a Red Hat product or service. For further information on how to report a security vulnerability to Red Hat please see the "Security Contacts and Procedures" page at https://www.redhat.com/security/team/contact/ Search 192836
SecurityTracking Bugs with the "SecurityTracking" keyword are those that relate to tracking security vulnerability with Red Hat products. For further information on how to report a security vulnerability to Red Hat please see the "Security Contacts and Services" page at https://www.redhat.com/security/team/contact/ Search 102108
SELinux Any bug associated with SELinux (Security Enhanced Linux). This includes bugs files directly against SELinux/kernel packages, as well as bugs related to policy or roles. Search 982
ServiceDeliveryBlocker A bug with this keyword has a serious impact on the delivery of a production service. Only use this for important issues that are urgent or affect the ability to adhere to a Service Level Agreement. Search 117
ServiceDeliveryImpact A bug with this keyword has an impact on the delivery of a production service which is not considered serious enough to qualify as ServiceDeliveryBlocker. Search 276
StringChange A string change that would break translations is required to fix this bug. i.e. fix the bug before the string freeze. Search 167
StudentProject Indicates that the project is appropriate for a student doing coursework (moderate scope, not a blocker, not trivial). Search 90
SubBug A bug that needs to be fixed as part of a larger work effort. Search 482
SubFeature A feature that needs to be created as part of a larger work effort. Search 264
SubscriptionExperience Search for and group bugs related to customer Subscription Experience. Search 33
SubscriptionWatch This bug is known to be affecting the Subscription Watch application on cloud.redhat.com. Search 62
SubTask The sub-task of the bug. Search 143
SupportQuestion Keyword for Makara migrated support questions Search 172
Task A task that needs to be done. Search 328
TechPreview Technology Preview is planned for this package. Search 1015
TestBlocker A test blocker is a bug that prevents at least one test (test case) from being executed. Search 8510
TestBlockerForLayeredProduct A bug with this keyword prevents at least one test (or test case) on a Layered Product of this product from being executed. The keyword tracks a dependency and is not intended to be used directly on the Layered Product itself. (When using this keyword it is not necessary to set TestBlocker as well unless it is also a test blocker for the product itself.) Search 110
TestCannotAutomate Tests for bugs with this keyword cannot be automated. Testing must be performed manually. Search 64
TestCaseApproved this is for test cases review by developer, approved test cases Search 213
TestCaseNeeded A test case should be created to make sure this bug does not reappear in future releases and testing. Search 340
TestCaseNotNeeded No new test case is needed. Search 419
TestCaseProvided A test case has been provided by the reporter, assignee or contributor. Search 1502
TestCaseRejected this is for test cases reveiw by developer, reject test cases Search 7
TestDisabled This keyword indicates that one or more tests are failing because of this bug and they have been disabled and are being skipped. After the bug is fixed, these tests need to be reinstated. Search 7
TestOnly Use this when there is no code delivery involved, or for use when code is already upstream and will be incorporated automatically to the next release for testing purposes only. Search 16876
Tracking This bug is a tracking bug. That means that this bug is only used as a placeholder for a particular set of changes which are split over a number of different bugs. All those bugs can be set to block this Tracking bug, so we have an easy way to query the status of a larger project based on the dependency tree of the Tracking bug. Tracking bugs do not require a release flag or acks. Search 16312
Translation Bugs with the "Translation" keyword are items to improve the translation of a component. This could include adding missing translations or correcting translations in print, on-line help or manpages. Search 3642
Triaged Bugs with the "Triaged" keyword have been given appropriate Severity/Priority fields and then assigned to an appropriate internal milestone, marked MoveUpstream, or closed. Bugs should not be marked Triaged unless they are targetted for a specific release, targetted to move upstream, or closed. i.e. they should have a clearly-defined path to closure. If there's no clear path to closure for a near-future release and no upstream to report the bug to, the right thing is probably to resolve WONTFIX or DEFERRED. Search 272164
Unconfirmed Bugs with the "Unconfirmed" keyword have been entered into Bugzilla but not yet confirmed by Development that an actual bug exists. Search 1971
UpcomingRelease Bugs with this keyword will be scheduled for a future release. Search 666
UpcomingSprint Bugs with this keyword will be scheduled for a future sprint. Search 1278
UpgradeBlocker Bugs that would breach service level objectives for product upgrade. Primarily useful for products that decouple GA installable releases from their corresponding upgrade (eg, OpenShift 4). Search 215
Upgrades Bugs with this keyword are related to upgrades. Search 1809
Upstream This keyword means that the feature or bug fix in this bugzilla was already accepted upstream and will be inherited by a RHEL release. Search 2368
UsabilityStudyPriority UsabilityStudyPriority indicates that this issue was found during a usability study initiative between Red Hat's Quality Engineering and User eXperience Design teams. It should be prioritised because it has been shown to have a significant negative impact on the user experience. Search 74
UseCase Use this when the goal of the bug is a specific, deployable configuration or set of configurations. Search 30
UserExperience UserExperience allows bugs to be filtered based on user experience, this is critical for Red Hat customer feedback. Search 2178
UserStory A User Story. Search 63
VerifiedOnDev This bug has been verified by the QA team in the DEV or CI environment. Search 63
VerifiedUpstream This keyword can be added to bugs where QE can explicitly say these bugs will be verified by the upstream community. Search 122
WeaknessTracking Bugs with the "WeaknessTracking" keyword are those that relate to tracking security weaknesses with Red Hat products or services. For further information on how to report a security vulnerability to Red Hat please see the "Security Contacts and Services" page at https://www.redhat.com/security/team/contact/ Search 268
WorkAround Bugs with the "WorkAround" keyword cannot be fixed but a work around exists. Search 293
WorkItem Migrated work items from fogbugz Search 134
ZStream The Keyword "ZStream" is used for both Z and Y Stream bugs. A Z Stream bug with Keyword "ZStream" was approved for Extended Update Support (EUS) or was approved by the Security Response Team for a RHSA. A Y Stream bug with Keyword "ZStream" means that a fix must be committed to a Y Stream release because a fix was already released asynchronously via Z Stream and not including it would cause a regression. Description from Jiri Skrabal. Search 100134
ZStreamTracked Bugs with this keyword must be released by a specific date during a batch update or an async release. This bugs is actively tracked by the RHEL EUS/ZStream Program Manager to ensure his release. Search 122