搜尋問題
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
在 Google Issue Tracker 中搜尋問題時，系統會傳回符合指定搜尋條件的所有問題。您可以使用搜尋查詢語言指定搜尋條件。搜尋結果會以可自訂及儲存的表格形式傳回。
您可以透過問題搜尋功能，廣泛查詢 Issue Tracker 中的所有問題，也可以使用多個條件建立非常明確的查詢。請注意，雖然您可以搜尋特定元件中回報的問題，但結果中不會包含元件本身。如要進一步瞭解如何執行元件搜尋，請參閱尋找元件指南。
您可以使用 Issue Tracker 頂端的搜尋列執行所有搜尋作業。搜尋列提供自動完成功能，可協助您選取欄位和特定欄位值。
您可以開啟搜尋建構工具，使用搜尋列右側的下拉式按鈕，輕鬆執行更多進階搜尋。
你可以儲存搜尋內容。
搜尋參數
您可以使用搜尋建構工具，透過視覺化介面在 Issue Tracker 中建立搜尋內容。您可以使用視覺化介面建立搜尋，不必在搜尋查詢語言中手動建構搜尋條件。
只要按一下搜尋列右側的向下箭頭按鈕，即可啟用搜尋建構工具。接著，按一下右上角的關閉按鈕，即可切換回搜尋列。不過，一旦開始建立搜尋內容，如果 Issue Tracker 無法轉換您指定的條件，您可能會遇到切換至搜尋列的問題。在這些情況下，Issue Tracker 會傳回錯誤。
使用搜尋列進行搜尋
您可以使用搜尋列手動建構搜尋查詢。如要瞭解如何手動建構搜尋內容，請參閱：
在元件及其子項中搜尋
在搜尋查詢中指定元件時，Issue Tracker 只會搜尋與該特定元件相關的問題。不過，您可以選擇在搜尋建構工具和搜尋編輯器中，將搜尋範圍擴大至子項元件。
搜尋參數
元件文字欄位右側是子元件資料夾符號。如果符號已停用，搜尋作業只會使用您指定的確切元件，而會忽略與子元件相關的問題。如果已啟用符號 (如以下螢幕截圖所示)，則與所選元件和任何子項元件相關的問題都會計入相符項目。
搜尋列
如果您想比對與元件或其任何子元件相關的問題，請在元件 ID 編號後方使用 +。舉例來說，componentid:46046+ 會傳回與 ID 為 46046 的元件相關的問題，以及與 46046 子項相關的任何問題。
搜尋條件
搜尋列會顯示在目前瀏覽器視窗中，在 Issue Tracker 中執行上次搜尋時的條件。如果從視窗中未執行任何搜尋，搜尋列會空白。這可以是使用搜尋列、搜尋建構工具或搜尋編輯器進行的明確搜尋。也可以是使用熱門清單連結或左側導覽窗格中的連結啟動的隱含搜尋。
保留所有權利。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間：2025-07-25 (世界標準時間)。
[null,null,["上次更新時間：2025-07-25 (世界標準時間)。"],[[["\u003cp\u003eIssue Tracker's search functionality allows users to find issues based on specified criteria using a search query language, and the results are displayed in a customizable table.\u003c/p\u003e\n"],["\u003cp\u003eUsers can construct searches using the search bar, manually inputting query language, or leverage the search builder for a visual interface to define criteria without manual query language construction.\u003c/p\u003e\n"],["\u003cp\u003eSearches can be refined to include a component and its children by enabling the subcomponent symbol in the search builder or appending a "+" to the component ID in the search bar.\u003c/p\u003e\n"],["\u003cp\u003eThe search bar displays the criteria of the most recent search, whether explicitly performed or implicitly triggered through links.\u003c/p\u003e\n"]]],[],null,["# Issue searches\n\nAn issue search in Google Issue Tracker returns all issues that match the\nspecified search criteria. You specify the search criteria using the\n[search query language](/issue-tracker/concepts/search-query-language). Search results are returned as a\n[customizable and savable table](/issue-tracker/concepts/search-results).\n\nAn issue search lets you broadly query all issues in Issue Tracker, or to create\nvery specific queries using multiple conditions for a search. Note that while\nyou can search for issues that are reported in specific components, your results\ndon't include components themselves. For information on performing component\nsearches, see the guide on how to [find a component](../guides/find-a-component).\n\nYou perform all searches using the search bar that appears at the top of Issue\nTracker. The search bar has an autocomplete function that helps you select\nfields and certain field values.\n\nYou can open the [search builder](../guides/search-builder) which makes it easier to perform more\nadvanced searches by using the drop-down button on the right-hand side of the\nsearch bar.\n\nYou can [save searches](../concepts/saved-searches) that you create.\n\nSearch builder\n--------------\n\nThe search builder lets you construct a search in Issue Tracker using a visual\ninterface. You can use the visual interface to build a search without having to\nmanually construct search criteria in the [Search Query Language](/issue-tracker/concepts/search-query-language).\n\nYou can activate the search builder by clicking the down-arrow button at the\nright side of the search bar. You can then switch back to the search bar by\nclicking the close button in the top right corner. However, once you start\nbuilding a search, you might encounter problems switching to the search bar if\nIssue Tracker cannot convert the criteria you specify. In these cases, Issue\nTracker returns an error.\n\nSearch with the search bar\n--------------------------\n\nYou can construct a search query manually by using the search bar. For help\nconstructing a search manually, see:\n\n- [Search with the Search Bar](../guides/search-editor)\n- [Search Query Language](/issue-tracker/concepts/search-query-language)\n- [Search Query Reference](../references/search-query-language-labels)\n\nSearch within a component and its children\n------------------------------------------\n\nWhen you specify a [component](../concepts/components) in a search query, Issue\nTracker only searches for issues associated with that exact component. However,\nyou can choose to expand the search scope to child components in both the search\nbuilder and search editor.\n\n### Search builder\n\nTo the right of the component text field is a subcomponent folder symbol. If the\nsymbol is disabled, only the exact component you specify is used in the search,\nwhile issues associated with child components are ignored. If the symbol is\nenabled, such as in the following screenshot, issues associated with both the\ncomponent you selected and any of its child components are counted as matches.\n\n### Search bar\n\nIf you want to match issues that are associated with a component or any of its\nchild components, use a `+` after the component ID number. For example,\n`componentid:46046+` returns issues associated with the component whose ID\nnumber is 46046 and any issues associated with a child of 46046.\n\n\u003cbr /\u003e\n\nSearch criteria\n---------------\n\nThe search bar shows the criteria for the last search that was run in Issue\nTracker from the current browser window. If no search has been run from the\nwindow, the search bar is blank. This can be an explicit search using the search\nbar, search builder, or search editor. It can also be an implicit search\ninitiated using a hotlist link or a link in the left navigation pane."]]
