How GitHub Built Sub-Issues into Its Issue Tracking System
Briefly

GitHub has launched sub-issues, allowing developers to organize tasks hierarchically, facilitating better management of complex projects. Sub-issues break down larger tasks into smaller components and enable tracking of progress efficiently. The team faced a crucial decision in whether to modify existing functionalities or to create a new structure, ultimately opting for the latter, which required significant adjustments to data models and rendering logic. Automatic progress updates for parent issues are a key feature, and the data is managed using MySQL relationships, allowing for effective project management across various teams.
GitHub's introduction of sub-issues enables developers to organize tasks in a parent-child hierarchy, enhancing task management and project tracking by breaking down complex tasks.
The decision to create a new hierarchical structure rather than modifying existing task functionalities required substantial changes to data models and rendering logic.
Automatic updates of a parent issue's progress based on its sub-issues streamline the project management process, reducing the need for manual tracking and oversight.
The sub-issues feature, modeled with MySQL relationships and exposed via GraphQL endpoints, facilitates efficient and effective data retrieval for project teams.
Read at InfoQ
[
|
]