封鎖問題
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
本頁說明如何在 Google Issue Tracker 中,將一個問題阻擋另一個問題。
當一個問題阻斷另一個問題時,表示第一個問題必須先解決,才能解決第二個問題。封鎖功能僅供追蹤用途,Issue Tracker 本身不會強制執行封鎖。即使有待處理的問題阻止,您仍可將問題標示為「已修正」。
封鎖功能是雙向的,如果您將一個問題設為封鎖另一個問題,第一個問題會顯示為第二個問題的「Blockers」清單之一,而第二個問題則會顯示在第一個問題的「Blocking」清單中。
您必須對包含兩個問題的元件具備編輯問題 權限,才能設定阻斷關係。
已封鎖的問題
封鎖問題表示該問題應在解決其他問題後再解決。首先需要解決的是「阻斷」問題,其次則是「遭到阻斷」問題。一個問題可以同時阻斷或遭到多個問題阻斷。
封鎖不會對問題造成任何實際限制。也就是說,即使未對阻斷問題進行任何變更,仍可更新或關閉該問題。因此,請將封鎖視為追蹤或通知系統。至於如何回應遭封鎖的問題,則由負責解決問題的人員和團隊決定。
UI 位置
系統會在「Blocking」和「Dependencies」分頁中追蹤封鎖情況。舉例來說,如果您前往問題 A 的頁面,並將其設為封鎖問題 B,則問題 A 的頁面會在「Blocking」分頁中列出問題 B,而問題 B 的頁面則會在「Dependencies」分頁的「Blockers」部分列出問題 A。
「封鎖」和「封鎖器」部分的標題會顯示各部分的問題數量。/
前方的數字是未解決問題的數量,/
後方的數字則是問題總數。舉例來說,如果「Blocking」分頁顯示 2/5
,表示有 5 個問題會阻礙目前的問題,但其中只有 2 個問題尚未解決。
按一下「Dependencies」或「Blocking」分頁,畫面會顯示相關問題的表格。每個問題項目都有幾個部分,包括「狀態」、「問題標題」和「問題 ID」。
按一下該列即可前往該問題。
將某個問題設為遭其他問題封鎖
如要將某個問題設為遭其他問題阻斷,請按照下列步驟操作:
前往要封鎖的問題。
在頁面頂端附近的分頁中,按一下「依附元件」。
在「封鎖項目」部分附近,按一下「新增封鎖項目」。

有兩種方法可以輸入封鎖問題。

- 方法 2:輸入問題 ID。一次最多可新增多個 ID,並以半形逗號分隔。

按一下「確認」。
如果成功,系統就會將封鎖問題加入「Blockers」清單。
設定要阻擋的問題
如要將某個問題設為阻礙另一個問題,請按照下列步驟操作:
前往要封鎖的問題。
在頁面頂端附近的分頁中,按一下「封鎖」。
按一下「新增」。

有兩種方法可以輸入遭封鎖的問題。

- 方法 2:輸入問題 ID。一次最多可新增多個 ID,並以半形逗號分隔。

按一下「確認」。
如果成功,系統就會將遭到封鎖的問題加入「Blocking」清單。
後續步驟
保留所有權利。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間:2025-07-25 (世界標準時間)。
[null,null,["上次更新時間:2025-07-25 (世界標準時間)。"],[[["\u003cp\u003eThis page explains how to establish blocking relationships between issues in Google Issue Tracker, indicating one issue must be resolved before another.\u003c/p\u003e\n"],["\u003cp\u003eBlocking is for tracking and notification, it doesn't enforce restrictions; blocked issues can still be updated or closed independently.\u003c/p\u003e\n"],["\u003cp\u003eYou can set an issue to be blocked by another, or set an issue to block another, using the 'Dependencies' and 'Blocking' tabs, respectively.\u003c/p\u003e\n"],["\u003cp\u003eThe 'Blocking' and 'Dependencies' tabs allow viewing and managing the blocking relationships, with the number of open and total blocking issues indicated.\u003c/p\u003e\n"],["\u003cp\u003eYou need 'Edit Issues' permissions for the components of both issues to establish a blocking relationship.\u003c/p\u003e\n"]]],[],null,["# Block an Issue\n\nThis page shows how to block one [issue](../concepts/issues) with another issue\nin Google Issue Tracker.\n\nWhen one issue blocks another, it means that the first issue should be resolved\nbefore the second one is resolved. Blocking is intended for tracking purposes\nonly. Issue Tracker itself does not enforce blocking. An issue can be marked\n**Fixed** even if it has open issues blocking it.\n\nThe blocking feature is reciprocal. If you set one issue to block a second\nissue, the first appears as one of the **Blockers** list of the second, while\nthe second appears in the **Blocking** list of the first.\n\nYou must have **Edit issues** [permission](../concepts/access-control) for the\ncomponents that contain both issues in order to set the blocking relationship.\n\nBlocked issues\n--------------\n\nWhen you block an issue, you indicate that the issue shouldn't be resolved until\nanother issue is resolved. The issue that needs to be resolved first is the\n*blocking* issue, while the issue that will be resolved second is the *blocked*\nissue. An issue can block or be blocked by multiple issues at the same time.\n\nBlocking does not impose any actual restrictions on issues. That is, the blocked\nissue can still be updated or closed even if no changes are made to the blocking\nissue. For this reason, blocking should be thought of as a tracking or\nnotification system. Decisions regarding how to respond to a blocked issue are\nleft to the individuals and teams responsible for resolving the issue.\n\n### UI Location\n\nBlocking is tracked in the **Blocking** and **Dependencies** tabs. For example,\nif you go to Issue A's page and set it to block Issue B, then the page for Issue\nA lists Issue B in its **Blocking** tab, while the page for Issue B lists Issue\nA in its **Dependencies** tab under the **Blockers** section.\n\nThe title of the **Blocking** and **Blocker** sections show how many issues are\nin each. The number preceding the `/` is the number of open issues and the\nnumber following `/` is the total number of issues. For example, if the\n**Blocking** tab reads `2/5`, then there are 5 issues in total set that block\nthe current issue, but only 2 of those issues have yet to be resolved.\n\nClicking on either the **Dependencies** or **Blocking** tab displays a table of\nrelevant issues. Each issue entry has several parts, including **Status** ,\n**Issue Title** , and **Issue ID**.\n\nClick the row to navigate to that issue.\n\nSet an issue to be blocked by another\n-------------------------------------\n\nTo set an issue as blocked by another issue:\n\n1. Navigate to the issue that is to be blocked.\n\n2. In the tabs near the top of the page, click **Dependencies**.\n\n3. Near the section titled **Blockers** , click **Add blocker**.\n\n4. There are two options to enter the blocking issue.\n\n - Option 1: text search for the issue.\n\n - Option 2: enter the issue id(s). Multiple IDs, separated by commas, can be added at a time.\n\n5. Click **Confirm**.\n\n If successful, the blocking issue will be added to the **Blockers** list.\n\nSet an issue to block another\n-----------------------------\n\nTo set an issue as blocking another issue:\n\n1. Navigate to the issue that will be blocking.\n\n2. In the tabs near the top of the page, click **Blocking**.\n\n3. Click **Add**\n\n4. There are two options to enter the blocked issue.\n\n - Option 1: text search for the issue.\n\n - Option 2: enter the issue id(s). Multiple IDs, separated by commas, can be added at a time.\n\n5. Click **Confirm**.\n\n If successful, the blocked issue will be added to the **Blocking** list.\n\nWhat's next\n-----------\n\n- [Mark an issue as a duplicate of another issue](/issue-tracker/guides/duplicate-issue)"]]