the Chromium logo

The Chromium Projects

Life of a ChromeOS Bug

ChromeOS maintains two public issue trackers where you can report bugs and request features for core ChromeOS functionality. (For details on this issue tracker, see Reporting Bugs.

Reporting bugs is great (thank you!), but what happens to a bug report after you file it? This page describes the life of a bug.

Note: The ChromeOS Public Issue Tracker is intended only for bugs and feature requests related to core ChromeOS functionality, and is a technical tool for the Open Source community.

This isn't a customer support forum. For support information, see the Chromebook help center.

*** promo Here are the key stages in the life of a bug:

  1. A bug is filed, and has the state New.
  2. The internal team periodically reviews and triages bugs. Bugs are triaged into one of four buckets: New, Open, No-Action, or Resolved.
  3. Each bucket includes a number of states that provide more detail on the fate of the issue.
  4. Bugs marked Resolved will be included in a future release of ChromeOS.

Bucket details

We use the Status field in Issue Tracker to specify the status of an issue in the resolution process. This is consistent with the definitions specified in the [Issue Tracker documentation] (

New issues

New issues include bug reports that haven't been acted upon. The two states are: *** promo

Open issues

This bucket contains bugs that need action, but that are still unresolved, pending a change to the source code. *** promo

Typically, a bug starts in Assigned, and remains there until someone intends to resolve it, at which point it enters Accepted. However, note that this isn't a guarantee, and bugs can go directly from Assigned to one of the Resolved states.

In general, if a bug is in one of the Open states, the ChromeOS team has recognized it as a legitimate issue, and a high-quality contribution fixing that bug is likely to get accepted. However, it is impossible to guarantee the completion of a fix in time for any particular release.

No-Action issues

This bucket contains bugs that are deemed to not require any action. *** promo

Resolved issues

This bucket contains bugs that have had action taken, and are now considered resolved. *** promo


The states and lifecycle above are how we generally try to track software. However, ChromeOS contains a lot of software and gets a correspondingly large number of bugs. As a result, sometimes bugs don't make it through all the states in a formal progression. We try to keep the system up to date, but we tend to do so in periodic bug sweeps where we review the database and make updates.