Starting today, we’re working on facilitating better collaboration between you and the Google Cloud Platform product teams, by upgrading to Issue Tracker, a tool we also use internally at Google. We have migrated all issues from the old code.google.com tracker to the new Issue Tracker hosted at issuetracker.google.com.
|Left: Google Code issue tracker, right: new Google Issue Tracker|
Getting started with Google Issue Tracker should be easy. Check out our documentation for more information about how to create, edit, search and group issues. By default, Google Issue Tracker only displays issues assigned to you, but you can easily change that to show a hotlist of your choice, a bookmark group or saved searches. You can also adjust notification settings by clicking the gear icon in the top right corner and selecting settings. For more information, check out the discussion of notification levels in the developer documentation.
|The Google App Engine open issues saved search|
GCP team wants your feedback!Starring an issue shows us you're interested in getting it fixed/implemented — please take advantage of this feature. It also allows you to quickly view all issues you starred.
Searching for product-specific issuesOpening any code.google.com issue link will automatically redirect you to the new system. You’ll be able to find all of the issues from code.google.com in the Issue Tracker, including any issue you've reported, commented on or starred. If you feel like anything is missing, let us know (how meta!) — we have backups available!
Issue Tracker organizes issues into a component hierarchy. Starting at the Cloud Platform component, you can drill down to a particular product's issues. And because each product (and some product features) have their own component, you can easily search for them. For example, you can view all Google App Engine or Google Compute Engine issues, which correspond to the old tracker’s full issue list for App Engine and Compute Engine. You can find links to each product's issues in our support documentation. To search within those issues, leave the component ID in the search bar; removing it will search public issues from all Google products.
For detailed instructions on how to create issues check out this guide, Still have questions? Take a peek at our FAQ. If you can’t find the answer please let us know by commenting on this post.
Please continue helping us improve our products by reporting issues and feature requests!