Managing your work with issues and pull requests

Use issues to track ideas, enhancements, tasks, or bugs for work on GitHub Enterprise Server.

Issues can be used to keep track of bugs, enhancements, or other requests.

People with admin permissions in a repository can permanently delete an issue from a repository.

You can open a new issue from a specific comment in an issue or pull request.

You can open a new issue from a specific line or lines of code in a file or pull request.

To move an issue to a better fitting repository, you can transfer open issues to other repositories.

You can pin up to three important issues above the issues list in your repository.

You can create a permanent link to a specific line or range of lines of code in a specific version of a file or pull request.

You can classify issues and pull requests by creating, editing, applying, and deleting labels.

You can use task lists to create a list of items with checkboxes within pull request and issue comments or Markdown files in your repository.

You can use query parameters to share URLs with customized information.

When you open issue or update a pull request, you can use issue attachments to upload images of proposed features or screenshots of bugs.

Assignees clarify who is working on specific issues and pull requests.

The Issues and Pull Request dashboards list the open issues and pull requests you've created. You can use them to update items that have gone stale, close them, or keep track of where you've been mentioned across all repositories—including those you're not subscribed to.

You may wish to turn issues off for your repository if you do not accept contributions or bug reports.

You can link a pull request to an issue to show that a fix is in progress and to automatically close the issue when the pull request is merged.

Mark an issue or pull request as a duplicate to track similar issues or pull requests together and remove unnecessary burden for both maintainers and collaborators.