github-docs-arabic-enhanced / content /issues /tracking-your-work-with-issues /learning-about-issues /quickstart.md
| title: Quickstart for GitHub Issues | |
| intro: 'Follow this brief interactive guide to learn about {% data variables.product.prodname_github_issues %}.' | |
| allowTitleToDifferFromFilename: true | |
| versions: | |
| fpt: '*' | |
| ghes: '*' | |
| ghec: '*' | |
| type: quick_start | |
| topics: | |
| - Issues | |
| - Project management | |
| redirect_from: | |
| - /issues/tracking-your-work-with-issues/quickstart | |
| - /issues/tracking-your-work-with-issues/configuring-issues/quickstart | |
| ## Introduction | |
| This guide demonstrates how to use {% data variables.product.prodname_github_issues %} to plan and track a piece of work. In this guide, you will create a new issue{% ifversion sub-issues %} and break it down into sub-issues{% endif %}. You'll also learn how to add labels{% ifversion issue-types %}, issue types{% endif %}, milestones, assignees, and projects to communicate metadata about your issue. | |
| ## Prerequisites | |
| To create an issue, you need a repository. You can use an existing repository that you have write access to, or you can create a new repository. {% data reusables.enterprise-accounts.emu-permission-repo %} The repository must have issues enabled. For more information about creating a repository, see [AUTOTITLE](/repositories/creating-and-managing-repositories/creating-a-new-repository). For more information about enabling issues if they are disabled in your repository, see [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-issues). | |
| ## Opening a blank issue | |
| First, create an issue. There are multiple ways to create an issue; you can choose the most convenient method for your workflow. This example will use the {% data variables.product.prodname_dotcom %} UI. For more information about other ways to create an issue, see [AUTOTITLE](/issues/tracking-your-work-with-issues/creating-an-issue). | |
| {% data reusables.repositories.navigate-to-repo %} | |
| {% data reusables.repositories.sidebar-issues %} | |
| {% data reusables.repositories.new_issue %} | |
| 1. In this example, we will start with a blank issue. Your repository may use issue templates{% ifversion fpt or ghec %} and issue forms{% endif %} to encourage contributors to provide specific information. If your repository uses issue templates, click **Open a blank issue**. | |
| ## Filling in information | |
| Give your issue a descriptive title. The title should convey at a glance what the issue is about. | |
| Add a description that explains the purpose of the issue, including any details that might help resolve the issue. For example, if this is a bug report, describe the steps to reproduce the bug, the expected result, and the actual result. | |
| You can use markdown to add formatting, links, emojis, and more. For more information, see [AUTOTITLE](/get-started/writing-on-github). | |
|  | |
| {% ifversion sub-issues %} | |
| ## Adding a task list | |
| You can also use plain text to track tasks that don't have a corresponding issue and convert them to issues later. For more information, see [AUTOTITLE](/get-started/writing-on-github/working-with-advanced-formatting/about-task-lists). | |
|  | |
| ## Assigning the issue | |
| To communicate responsibility, you can assign the issue to a member of your organization. See [AUTOTITLE](/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users). | |
|  | |
| ## Adding labels | |
| Add a label to categorize your issue. For example, you might use a `question` label and a `good first issue` label to indicate that an issue is a question that a first-time contributor could pick up. Users can filter issues by label to find all issues that have a specific label. | |
| You can use the default labels, or you can create a new label. For more information, see [AUTOTITLE](/issues/using-labels-and-milestones-to-track-work/managing-labels). | |
|  | |
| {% ifversion issue-types %} | |
| ## Adding issue types | |
| You can add an issue type to classify work across the organization. See [AUTOTITLE](/issues/tracking-your-work-with-issues/using-issues/managing-issue-types-in-an-organization). | |
|  | |
| {% endif %} | |
| ## Adding the issue to a project | |
| You can add the issue to an existing project and populate metadata for the project. For more information about projects, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects). | |
|  | |
| ## Adding milestones | |
| You can add a milestone to track the issue as part of a date based target. A milestone shows the progress of the issues as the target date approaches. See [AUTOTITLE](/issues/using-labels-and-milestones-to-track-work/about-milestones). | |
|  | |
| ## Submitting your issue | |
| Click **Submit new issue** to create your issue. You can edit any of the above fields after creating the issue. Your issue has a unique URL that you can share with team members, or reference in other issues or pull requests. | |
| ## Adding sub-issues | |
| {% data reusables.issues.about-sub-issues %} See [AUTOTITLE](/issues/tracking-your-work-with-issues/using-issues/adding-sub-issues) and [AUTOTITLE](/issues/tracking-your-work-with-issues/using-issues/browsing-sub-issues). | |
|  | |
| {% endif %} | |
| ## Adding 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 [AUTOTITLE](/free-pro-team@latest/issues/tracking-your-work-with-issues/using-issues/creating-issue-dependencies). | |
| ## Communicating | |
| After your issue is created, continue the conversation by adding comments to the issue. You can @mention collaborators or teams 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. For more information, see [AUTOTITLE](/get-started/writing-on-github). | |
|  | |
| ## Next steps | |
| You can use issues for a wide range of purposes. For example: | |
| * Tracking ideas | |
| * Collecting feedback | |
| * Planning tasks | |
| * Reporting bugs | |
| {% ifversion sub-issues %} | |
| To break your issue down into more manageable tasks, you can add multiple levels of sub-issues. See [AUTOTITLE](/issues/tracking-your-work-with-issues/using-issues/adding-sub-issues). | |
| {% endif %} | |
| Here are some helpful resources for taking your next steps with {% data variables.product.prodname_github_issues %}: | |
| * To learn more about issues, see [AUTOTITLE](/issues/tracking-your-work-with-issues/about-issues). | |
| * To learn about the essentials for using {% data variables.product.github %}'s planning and tracking tools, see [AUTOTITLE](/issues/tracking-your-work-with-issues/learning-about-issues/planning-and-tracking-work-for-your-team-or-project). | |
| * To learn more about how projects can help you with planning and tracking, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/learning-about-projects). | |
| * To learn more about using issue templates{% ifversion fpt or ghec %} and issue forms{% endif %} to encourage contributors to provide specific information, see [AUTOTITLE](/communities/using-templates-to-encourage-useful-issues-and-pull-requests). | |