Issue

Issues are used as a good way to track project tasks, improvements, and bugs.
Project planning, newly added features, bugs, and fixes can all be referred to as issues.
You can register issues for all activity details and proceed with work based on the registered issues.
GitHub uses issues to handle ideas, work, and bugs (problems) among developers.
- Discussions about idea implementation
- Tracking work progress
- Accepting feature limitations, questions, support requests, or bug reports
- Sophisticated code implementation
To register an issue, you usually follow these steps:
- Click to open the Issues tab.
- Provide as much information (context) as possible to reproduce the problem or situation.
- Provide all information you think is relevant, such as environment details (version, OS, etc.).
Once an issue is registered, it usually goes through these steps:
- The project team (or manager) assigns labels and an assignee.
- The assignee tries to respond as quickly as possible.
- If it's resolved or there's no response for a long time, the issue is closed.

Core developers and managers of the project create templates to prevent misuse of issues.
On GitHub, issue templates are written under the .github folder.
@mentions: Sends a notification to the person with that ID.
#reference: Used with a number like #9999. Refers to another issue.
/cc: Abbreviation for Carbon Copy, meaning reference. Append a mention after it.
/assign: Append a mention after it to assign an assignee.
/milestone: A feature for setting agile sprint times.
/label: Attach labels to manage various issues.
/due: Specifies a target date.

When a solved problem is submitted as a merge request, the project manager merges it with the main branch.