Go Wiki: HandlingIssues

This document explains how we handle issue triage and scheduling in the Go project’s issue tracker.

Issue States

Any issue must be in one of the following states. Project contributors move issues from one state to another. The intent behind these explicit states is to describe the (minimum) next steps required to bring the issue to resolution. Issues may move between states in any order, as dictated by the needs of the particular issue.


Needs Investigation

Needs Decision

Needs Fix

Fix Pending


Issues move from one state to another where appropriate. For example, a contributor may file an issue, assign it to themselves, and immediately apply the NeedsFix label. Or, an issue may go from NeedsDecision to NeedsFix, only to later move back to NeedsDecision as complexities arise.

An issue may be closed at any time, with a comment to indicate the reason for closure (“fixed by …”, “duplicate of …”, “working as intended”, etc).

At any state (except New) the issue may be assigned to someone. Unassigned issues are considered available for anyone to address.


Milestones describe the timeline for issue resolution.

Additional milestones may be used to manage specific project work.

The label “Soon” is used independently of milestones to indicate that the issue is time-sensitive.

This content is part of the Go Wiki.