Issues
Issues give your team a shared place to track bugs, plan features, and capture anything that needs attention — all linked directly to the code in your repository.
Create an Issue
Section titled “Create an Issue”- Open your repository and select the Issues tab.
- Select New Issue.
- Enter a concise Title that describes the problem or task.
- Write a Description using Markdown — include reproduction steps, acceptance criteria, screenshots, or code blocks as needed.
- Select Submit New Issue to publish it.
Organize with Labels and Milestones
Section titled “Organize with Labels and Milestones”Labels categorize and prioritize issues. Apply one or more labels from the right-hand sidebar when viewing an issue, or directly from the issue list using the Label filter. Common conventions are type labels (bug, enhancement) alongside priority labels (high, low), but you can create any labels that fit your workflow under Issues → Labels.
Milestones group issues toward a shared target — a release date, a sprint, or a feature goal. Create milestones under Issues → Milestones, then assign an issue to a milestone from its sidebar. The milestone view shows progress as issues close.
Assign and Discuss
Section titled “Assign and Discuss”- Assignees — use the Assignees field in the sidebar to indicate who is responsible. Any workspace member with repository access can be assigned.
- Comments — add context, decisions, or status updates in the comment thread below the issue description.
- @mentions — type
@usernameanywhere in a comment or description to notify that person directly. - Reactions — use emoji reactions on comments to acknowledge a point without adding a reply.
Link Issues to Code
Section titled “Link Issues to Code”Referencing issues from commits and pull requests keeps your history traceable.
- Reference by number — type
#12in a commit message, pull request description, or comment to create a clickable link to issue 12 in the same repository. - Auto-close on merge — include a closing keyword in a pull request description (for example,
Closes #12,Fixes #34, orResolves #56). When the pull request merges into the default branch, the referenced issues close automatically. - Cross-reference other issues — use
#numberfreely in any issue comment to link related issues; each referenced issue displays a back-link so the connection is visible from both sides.
Find Issues
Section titled “Find Issues”The issue list supports several filters you can combine:
| Filter | What It Does |
|---|---|
| State | Show open or closed issues |
| Label | Narrow to one or more labels |
| Milestone | Show issues assigned to a milestone |
| Assignee | Show issues assigned to a specific person |
| Author | Show issues opened by a specific person |
Select the appropriate column in the filter bar above the issue list to apply each filter. To search across issue titles and bodies with keywords, see Searching Code.