[null,null,["最后更新时间 (UTC):2025-07-25。"],[[["\u003cp\u003eGoogle Issue Tracker uses Components to organize issues into logical groups, which can be nested to create a hierarchy.\u003c/p\u003e\n"],["\u003cp\u003eComponents have properties like name, ID, description, and custom fields, and allow for access control and templates for issues.\u003c/p\u003e\n"],["\u003cp\u003eIssue Tracker provides a component search tool to easily find and select components when creating or editing issues.\u003c/p\u003e\n"],["\u003cp\u003eComponent hovercards offer quick access to view recent issues, create new issues within the component, and view component details.\u003c/p\u003e\n"],["\u003cp\u003eRecently used components are readily accessible for quicker issue creation and management.\u003c/p\u003e\n"]]],[],null,["# Components are containers for [issues](/issue-tracker/concepts/issues) in Google Issue Tracker. A component\nmay correspond to a project, sub-project or other functional or organizational\ngroup of issues.\n\nComponents can have child components, with all of the components in Issue\nTracker comprising a component hierarchy. Generally, the hierarchy organizes\ncomponents from most general to most specific. For example, a project whose\nissues are managed in Issue Tracker can have one top-level component and several\nnested sub-components, each of which organize issues into related groups.\n\nA best practice for creating issues is to create them in the most specific\ncomponent whose purpose matches the issue type. The appropriate component for\nany given issue varies by project.\n\nComponent properties\n--------------------\n\nComponents have the following properties:\n\n| Property | Example | Description |\n|-------------------------|----------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|\n| **Name** | Feedback | Name of the component. This is not necessarily unique across Issue Tracker. |\n| **ID** | 121405 | Unique ID number for the component. |\n| **Description** | Summary of information required to identify the component and its purpose. | |\n| **Component Hierarchy** | `Sample Project \u003e Sample Project Bugs` | Hierarchy of the parent components down to the given component. |\n| **Child Components** | `UX Bugs`, `Latency Issues`, `Security` | Components that are direct children of the given component. |\n| **Custom Fields** | `Sprint`, `ETA` | Custom fields associated with the component. For more information, see [Custom Fields](/issue-tracker/concepts/custom-fields). |\n| **Access Control** | See [Access Control](/issue-tracker/concepts/access-control) | Specifies who can perform what actions in the component. |\n| **Templates** | See the [Template page](/issue-tracker/concepts/templates) | Specifies default or initial fields values for new issues filed in the component. |\n\nComponent search\n----------------\n\nIssue Tracker displays the [component search tool](../guides/find-a-component) wherever you can specify a\ncomponent in the user interface. When you enter keywords associated with the\ncomponent path or description, the tool automatically initiates a component\nsearch and displays ranked search results in a drop-down list. The ranking is\ndetermined using a combination of text-match scoring and popularity.\n\n| If you search components using a string of numbers, Issue Tracker returns components that have the string in their name or description, as well as the specific component whose component ID matches the string.\n\nThe component search result shows matching components, as well as any child\ncomponents.\n\nTo isolate a specific component within the displayed hierarchy and view its\nchildren, click the **Show Child Components** button\n\non the left side of the component entry. This button is not available when using\nthe search bar. When you click the button the component tree browser replaces\nthe ranked search results.\n\nYou can click the back button to return to the ranked search results.\n\n#### Search for components\n\nYou can search for components when you perform the following tasks:\n\n- [Create a new issue](../guides/create-issue-ui).\n- [Edit the component field of a specific issue](../guides/edit-issue-ui).\n- Choose **Component** in the [search builder](/issue-tracker/concepts/searches).\n- Enter `componentID` in the [search bar](/issue-tracker/concepts/searches).\n- Select **Component** in the Edit drop-down of a [*bulk edit*](../guides/edit-issue-bulk).\n- Search by or display a [custom field](/issue-tracker/concepts/custom-fields) in an issue search.\n\n| When you search for a component in the search bar, you cannot choose to show child components when viewing search results. These features also convert any component name that you choose to a numerical ID for display.\n\nComponent hovercards\n--------------------\n\nA component hovercard contains the component name, ID, and description. For\nexample:\n\nThe component hovercard contains three links:\n\n- **View recent open issues**: Link that searches for open issues assigned to the component and orders the results by date of creation.\n- **Create an issue in this component** : Link that takes you to a [Create Issue page](../guides/create-issue-ui) with the component and template pre-selected.\n- **View component**: Link that takes you to the manage component page for the component.\n\nComponent hovercards appear when hovering over the following:\n\n- A component within the component hierarchy, as listed below the issue title on an issue details page.\n- Components in the **Component Hierarchy** or **Child Components** section of the **Basic Information** tab of a component details page.\n- Components listed in the **Custom Fields** section of the **Fields** tab on the component details page.\n\nRecent Components\n-----------------\n\nWhen you click **Search Components** , recently used components appear in the\npicker below the search box. Recently used components also appear on the\n**Browse components** page.\n\nComponents are considered recent if you have done any of the following while\nlogged in:\n\n- Created an issue in the component\n- Edited an issue in the component"]]