{"meta":{"title":"Issue manager","intro":"Create well-structured issues and responses.","product":"GitHub Copilot","breadcrumbs":[{"href":"/en/copilot","title":"GitHub Copilot"},{"href":"/en/copilot/tutorials","title":"Tutorials"},{"href":"/en/copilot/tutorials/customization-library","title":"Customization library"},{"href":"/en/copilot/tutorials/customization-library/custom-instructions","title":"Custom instructions"},{"href":"/en/copilot/tutorials/customization-library/custom-instructions/issue-manager","title":"Issue manager"}],"documentType":"article"},"body":"# Issue manager\n\nCreate well-structured issues and responses.\n\n> \\[!NOTE]\n>\n> * The examples in this library are intended for inspiration—you are encouraged to adjust them to be more specific to your projects, languages, and team processes.\n> * For community-contributed examples of custom instructions for specific languages and scenarios, see the [Awesome GitHub Copilot Customizations](https://github.com/github/awesome-copilot/blob/main/docs/README.instructions.md) repository.\n> * You can apply custom instructions across different scopes, depending on the platform or IDE where you are creating them. For more information, see \"[About customizing GitHub Copilot responses](/en/copilot/concepts/response-customization).\"\n\nThe following example shows custom instructions to guide GitHub Copilot to create well-structured, actionable GitHub issues and provide effective issue management.\n\n```markdown copy\nWhen creating or managing GitHub issues:\n\n## Bug Report Essentials\n**Description**: Clear, concise summary of the problem\n\n**Steps to Reproduce**: Numbered list of exact actions that cause the issue\n\n**Expected vs Actual Behavior**: What should happen vs what actually happens\n\n**Environment**: OS, browser/client, app version, relevant dependencies\n\n**Additional Context**: Screenshots, error logs, or stack traces\n\n## Feature Request Structure\n**Problem**: What specific problem does this solve?\n\n**Proposed Solution**: Brief description of the suggested approach\n\n**Use Cases**: 2-3 concrete examples of when this would be valuable\n\n**Success Criteria**: How to measure if the feature works\n\n## Issue Management Best Practices\n- Use clear, descriptive titles that summarize the request\n- Apply appropriate labels: bug/feature, priority level, component areas\n- Ask clarifying questions when details are missing\n- Link related issues using #number syntax\n- Provide specific next steps and realistic timelines\n\n## Key Response Guidelines\n- Request reproduction steps for unclear bugs\n- Ask for screenshots/logs when visual issues are reported\n- Explain technical concepts clearly for non-technical users\n- Update issue status regularly with progress information\n\nFocus on making issues actionable and easy for contributors to understand.\n```\n\n## Further reading\n\n* [About customizing GitHub Copilot responses](/en/copilot/concepts/response-customization) - Overview of response customization in GitHub Copilot\n* [Add custom instructions for Copilot](/en/copilot/how-tos/configure-custom-instructions) - How to configure custom instructions\n* [Awesome GitHub Copilot Customizations](https://github.com/github/awesome-copilot/blob/main/README.md) - Repository of community-contributed custom instructions and other customizations for specific languages and scenarios"}