The tool Google uses internally to track bugs and feature requests, as well as collecting feedback, has now been made available to Android Open-Source Project (AOSP) developers. More specifically, this is the same issue tracking tool the search giant behind Android has been using to track those issues for the Android O Developer Preview. The public release was announced on April 14 and is intended to bring greater collaboration between Google's Android product teams and AOSP developers.
As part of the tool's new public release, some of the information that used to be found at the dedicated code.google Android issues website have also been migrated. According to Google, those include all open and closed issues filed by a developer, all issues "starred" by a developer and all issues a developer has commented on. For those new to the issue tracker, the company has set up a wealth of separate pages - links to which can be found at the source - for learning to use it but Google says that the tool will show developers their "assigned" issues by default. That should make jumping right in a bit easier. However, AOSP devs should also be aware that status mappings work a bit differently from the old website, so it may take some getting used to and they may want to refer to the guides mentioned above. As well as the added perk of having links to issues from the previously used site open with the new system, Google says it has cut back on spam significantly with the issue tracker. Moreover, the new tool allows an AOSP developer to find issues by category.
All of that aside, Google also took the opportunity with the announcement to remind devs to make sure they search to see if an issue has already been reported before creating a new issue listing. Since this is the tool Google has been using internally, it makes sense that the search giant wouldn't want it to get bogged down by duplicate reports. Google also recommends "starring" any such issue if it has already been reported, so that developers can get a sense of which issues need to be prioritized.