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 프로젝트 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 문제 만들기.

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

문제에 하위 문제를 추가하여 더 큰 업무를 작업으로 빠르게 나눌 수 있습니다. 하위 문제는 문제 간의 관계를 만들어 GitHub에서 문제의 계층 구조에 대한 지원을 추가합니다. 작업을 자신과 팀에 필요한 세부 정보로 정확하게 분류하여 프로젝트를 정확하게 나타내는 여러 수준의 하위 문제를 만들 수 있습니다. See 하위 이슈 추가 and 하위 이슈 찾아보기.

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 끌어오기 요청을 이슈에 연결.

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 사용자에게 문제 할당 및 끌어오기 요청 and 모든 문제 및 끌어오기 요청 보기.

Community management

To help contributors open meaningful issues that provide the information that you need, you can use issue forms and issue templates. See 템플릿을 사용하여 유용한 이슈 및 끌어오기 요청 권장.

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 사용자에게 문제 할당 및 끌어오기 요청.

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: