Components are containers for issues in Google Issue Tracker. A component may correspond to a project, sub-project or other functional or organizational group of issues.

Components can have child components, with all of the components in Issue Tracker comprising a component hierarchy. Generally, the hierarchy organizes components from most general to most specific. For example, a project whose issues are managed in Issue Tracker can have one top-level component and several nested sub-components, each of which organize issues into related groups.

A best practice for creating issues is to create them in the most specific component whose purpose matches the issue type. The appropriate component for any given issue varies by project.

Component properties

Components have the following properties:

Property Example Description
Name Feedback Name of the component. This is not necessarily unique across Issue Tracker.
ID 121405 Unique ID number for the component.
Description Summary of information required to identify the component and its purpose.
Component Hierarchy Sample Project > Sample Project Bugs Hierarchy of the parent components down to the given component.
Child Components UX Bugs, Latency Issues, Security Components that are direct children of the given component.
Custom Fields Sprint, ETA Custom fields associated with the component. For more information, see Custom Fields.
Access Control See Access Control Specifies who can perform what actions in the component.
Templates See the Template page Specifies default or initial fields values for new issues filed in the component.

Issue Tracker displays the component search tool wherever you can specify a component in the user interface. When you enter keywords associated with the component path or description, the tool automatically initiates a component search and displays ranked search results in a drop-down list. The ranking is determined using a combination of text-match scoring and popularity.

The component search result shows matching components, as well as any child components.

To isolate a specific component within the displayed hierarchy and view its children, click the Show Child Components button on the left side of the desired entry. (Note that this button is not available when using the search bar.) When you click the button the component tree browser replaces the ranked search results.

You can click the back button to return to the ranked search results.

Search for components

You can search for components when you perform the following tasks:

Component hovercards

A component hovercard contains the component name, ID, and description. It also contains three links:

  • View Recent Issues: Link that searches for open issues assigned to the component and orders the results by date of creation.
  • Create an Issue in This Component: Link that takes you to a Create Issue page with the component and template pre-selected.
  • View component: Link that takes you to the Component Manager page for the component. For example:

Component hovercards appear when hovering over the following:

  • A component within the component hierarchy, as listed below the issue title on an issue details page.
  • Components in the Component Hierarchy or Child Components section of the Basic Information tab of a component details page.
  • Components listed in the Custom Fields tab of a component details page.

Recent Components

When you click Search Components, recently used Components appear in the picker below the search box. Recently used components also appear on the Browse Components page.

Components are considered recent if you have done any of the following while logged in:

  • Created an issue in the component
  • Edited an issue in the component