Stay organized with collections
Save and categorize content based on your preferences.
A tracker is a scoped version of Google Issue Tracker used by some open source
projects. A tracker view shows only issues and components that belong to the
tracker, letting you focus on work that is relevant to your project. Trackers
can also have custom branding with a unique URL, logo, and color theme.
Features
Trackers include several features:
You can access a tracker from a custom domain. For example, you can access
the Pigweed tracker from
https://issues.pigweed.dev.
You see a branded instance of Google Issue Tracker. For example, the Pigweed
tracker shows Pigweed logo and header, open source themed buttons, and a
footer with Pigweed branding.
Tracker admins can configure trusted collaborator groups. Issue admins
can add these groups as collaborators on issues from the
issue access limits
dialog:
Alternatively, issue admins can add trusted collaborator groups to
issues on the create issue page:
Access non-tracker issues from a tracker
You can access your hotlists, saved searches and
bookmark groups when using a tracker. However, some issues
may not be visible, since issues outside of the tracker are not displayed.
When you view an issue not belonging to the tracker, you will be redirected
outside the tracker.
View tracker information
When you are not in a tracker, tracker chips are displayed for issues and
components belonging to a tracker.
When you view a tracker issue from outside of a tracker, you see a banner with a
link to view the issue in the tracker.
You can search for issues by tracker using the trackerid field in the search
bar.
You can also search for issues in a tracker using the search builder.
All rights reserved. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-02-12 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-02-12 UTC."],[[["\u003cp\u003eA tracker is a customized version of Google Issue Tracker with unique branding (URL, logo, and color theme) used by some open source projects for focused issue management.\u003c/p\u003e\n"],["\u003cp\u003eTrackers provide a dedicated view of issues and components relevant to a specific project, enhancing collaboration and organization.\u003c/p\u003e\n"],["\u003cp\u003eUsers can access trackers from custom domains, see branded elements within the tracker, and easily manage project-specific issues.\u003c/p\u003e\n"],["\u003cp\u003eWhile focused on a project, trackers allow referencing external issues and maintain access to personal hotlists, saved searches, and bookmark groups.\u003c/p\u003e\n"],["\u003cp\u003eIssues belonging to a tracker can be identified by tracker chips and viewed within their dedicated tracker context even when accessed from outside.\u003c/p\u003e\n"]]],[],null,["# Trackers\n\nA tracker is a scoped version of Google Issue Tracker used by some open source\nprojects. A tracker view shows only issues and components that belong to the\ntracker, letting you focus on work that is relevant to your project. Trackers\ncan also have custom branding with a unique URL, logo, and color theme.\n\nFeatures\n--------\n\nTrackers include several features:\n\n- You can access a tracker from a custom domain. For example, you can access\n the Pigweed tracker from\n \u003chttps://issues.pigweed.dev\u003e.\n\n- You see a branded instance of Google Issue Tracker. For example, the Pigweed\n tracker shows Pigweed logo and header, open source themed buttons, and a\n footer with Pigweed branding.\n\n- You only see [issues](/issue-tracker/concepts/issues) and [components](/issue-tracker/concepts/components) belonging to the\n tracker.\n\n | **Note:** Although autocomplete suggestions only show issues that belong to the tracker, you can add issue dependencies from outside of the tracker by specifying the Issue ID. For example: You can still use blocking and blocked by to reference an issue that is external to the tracker. For more information, see [Blocking an issue](../guides/block-issue).\n- Tracker admins can configure trusted **collaborator groups** . Issue admins\n can add these groups as **collaborators** on issues from the\n [issue access limits](https://developers.google.com/issue-tracker/concepts/issues#issue_access_limits)\n dialog:\n\n- Alternatively, issue admins can add trusted **collaborator groups** to\n issues on the create issue page:\n\nAccess non-tracker issues from a tracker\n----------------------------------------\n\nYou can access your [hotlists](/issue-tracker/concepts/hotlists), [saved searches](/issue-tracker/concepts/saved-searches) and\n[bookmark groups](/issue-tracker/concepts/bookmark-groups) when using a tracker. However, some issues\nmay not be visible, since issues outside of the tracker are not displayed.\n\nWhen you view an issue not belonging to the tracker, you will be redirected\noutside the tracker.\n\nView tracker information\n------------------------\n\nWhen you are not in a tracker, tracker chips are displayed for issues and\ncomponents belonging to a tracker.\n\nWhen you view a tracker issue from outside of a tracker, you see a banner with a\nlink to view the issue in the tracker.\n\nYou can search for issues by tracker using the `trackerid` field in the search\nbar.\n\nYou can also search for issues in a tracker using the search builder.\n\nFor more information, see:\n\n- [Searching with the Search Bar](/issue-tracker/concepts/search-editor)\n- [Searching with the Search Builder](/issue-tracker/concepts/search-builder)\n- [Search Query Reference](../references/search-query-language-labels)"]]
