[FR] Support for Parent-Child Issues

Problem

The Copilot Coding Agent is currently triggered by assigning it to an individual issue. However, GitHub now supports parent-child relationships between issues. This creates a disconnect where a parent issue, representing a larger task, cannot leverage the Copilot Coding Agent to automatically manage and work on its constituent child issues. This limitation prevents the agent from contributing to larger, decomposed work efforts, requiring manual intervention for each sub-task.

Solution

Enable the Copilot Coding Agent to operate on parent issues with linked child issues. When the Copilot Coding Agent is assigned to a parent issue, it should:

• Identify Child Issues: Automatically recognize and access all linked child issues.
• Distribute Work: Distribute or contribute to the tasks outlined in the child issues, working towards the completion of the overall parent issue.
• Track Progress: Reflect progress across child issues to the parent issue's overall status.

Benefits

• Automated Management of Complex Tasks: Allows the Copilot Coding Agent to tackle larger, multi-part projects by breaking them down into manageable sub-tasks.
• Increased Efficiency: Reduces manual effort required to assign the agent to individual child issues, streamlining the workflow for complex features or epics.
• Improved Project Visibility: Provides a consolidated view of agent progress on a larger task by reflecting work across child issues.
• Enhanced Collaboration: Facilitates a more organized approach to complex development, where the agent can contribute to various aspects of a larger goal.

Examples

• Feature Development: A parent issue "Implement User Authentication" could have child issues like "Create Login Page UI," "Develop User Registration API," and "Integrate Session Management." Assigning Copilot to the parent issue would allow it to work on each of these sub-components.
• Bug Fix Rollout: A parent issue "Address Critical Security Vulnerability" might have child issues for "Patch Frontend," "Update Backend API," and "Deploy Hotfix to Production." The agent could assist with each of these steps from the parent assignment.
• Documentation Sprint: A parent issue "Revise API Documentation" could be broken into child issues for "Document Authentication Endpoints," "Add Examples for Data Models," and "Review OpenAPI Specification." The Copilot Coding Agent could contribute to generating or refining content for each section.

[beingminimal]

@nhu-do any ETA for this feature?

[beingminimal]

@nhu-do with this release of github mcp server 0.9.0 now child issues can be auto supported in coding agent? Please reply