Skip to main content

About issues

Learn how you can use GitHub Issues to track ideas, feedback, tasks, or bugs.

You can create issues in your repository to plan, discuss, and track work. Issues are quick to create, flexible, and can be used in many ways. Issues can track bug reports, new features and ideas, and anything else you need to write down or discuss with your team, and you can use projects to plan and track the work for your team. You can also break your work down further by adding sub-issues and easily browse the full hierarchy of work to be done.

Issues can be created in a variety of ways, so you can choose the most convenient method for your workflow. For example, you can create an issue from a repository, while adding sub-issues, convert a comment in an issue or pull request, create an issue from a specific line of code, or via a URL query. You can also create an issue from your platform of choice: through the web UI, GitHub Desktop, GitHub CLI, GraphQL and REST APIs, or GitHub Mobile. See Issue の作成.

ヒント

You can also use Copilot Chat to generate ideas, outlines, or drafts for discussions or blog posts, based on your issues. See ディスカッションまたはブログ記事を書く.

About sub-issues

sub-issue を issue に追加することで、大きな作業をタスクに簡単に分割できます。 sub-issue により、issue 間の関係が作成されて、GitHub での issue の階層のサポートが追加されます。 ユーザーやチームが必要とする詳細さにタスクを分割することでプロジェクトを正確に表す sub-issue の複数のレベルを作成することができます。 See sub-issue の追加 and sub-issue の閲覧.

About issue dependencies

You can define blocking relationships between issues using issue dependencies. Issue dependencies let you identify issues that are blocked by, or blocking, other work. See Creating issue dependencies.

Metadata on issues

You can add metadata to your issues, including issue types, labels and milestones to organize your issues.

See Managing issue types in an organization, ラベルを管理する and マイルストーンについて.

About integration with GitHub

Issues integrate with your work all across GitHub. Mentioning an issue in another issue or pull request will create references between them and using keywords, like fixes:, in your pull requests will automatically close the associated issues. See Pull RequestをIssueにリンクする.

Using プロジェクト to plan and track your work

プロジェクト is strongly integrated with issues to plan and track the work for your team. All your issue metadata is available in your projects, allowing you to create views and filters to represent your work. See Projects について.

Staying up to date

To stay updated on the most recent comments in an issue, you can subscribe to an issue to receive notifications about the latest comments. To quickly find links to recently updated issues you're subscribed to, visit your dashboard. For more information, see 通知について and Quickstart for your personal dashboard.

You can assign yourself and teammates to issues to make it clear who is working on an issue and also make it easier for you to locate your issues. See GitHub の他のユーザに Issue およびプルリクエストをアサインする and すべての issue と pull request の表示.

Community management

To help contributors open meaningful issues that provide the information that you need, you can use issue forms and issue templates. See テンプレートを使用して便利な Issue やプルリクエストを推進する.

To maintain a healthy community, you can report comments that violate GitHub's Community Guidelines. See 悪用あるいはスパムをレポートする.

Efficient communication

You can @mention collaborators who have access to your repository in an issue to draw their attention to a comment. To link related issues in the same repository, you can type # followed by part of the issue title and then clicking the issue that you want to link. To communicate responsibility, you can assign issues. If you find yourself frequently typing the same comment, you can use saved replies. See 基本的な書き方とフォーマットの構文 and GitHub の他のユーザに Issue およびプルリクエストをアサインする.

Comparing issues and discussions

Some conversations are more suitable for GitHub Discussions. GitHub Discussions を使用すると、質問、質問への回答、情報の共有、発表、および製品に関する会話や会話への参加を行うことができます。 詳しくは、「ディスカッションについて」をご覧ください。 For guidance on when to use an issue or a discussion, see GitHub でのコミュニケーション.

When a conversation in an issue is better suited for a discussion, you can convert the issue to a discussion.

Next steps

Here are some helpful resources for taking your next steps with GitHub Issues: