---
number: 7741
title: Manages GitHub issue relationships
author: MannXo
state: MERGED
createdAt: '2025-11-11T10:39:38Z'
updatedAt: '2025-11-12T08:20:30Z'
closedAt: '2025-11-12T08:20:30Z'
mergedAt: '2025-11-12T08:20:30Z'
head: feat/manage-issue-relationships-tool
base: dev
url: 'https://github.com/neomjs/neo/pull/7741'
---
#### Summary
Implemented the update_issue_relationship tool to manage parent-child relationships between GitHub issues.

#### What Was Built
1- GraphQL Mutations `mutations.mjs`
2- Service Method `IssueService.mjs`
3- OpenAPI Spec `openapi.yml`
4- Tool Registration  `toolService.mjs`
5- Markdown Format Update `IssueSyncer.mjs`

**Does this PR resolve an issue?** (Required)

Closes #7632 



**What kind of change does this PR introduce?** (check at least one)

- [ ] Bugfix
- [x] Feature
- [ ] Code style update
- [ ] Refactor
- [ ] Build-related changes
- [ ] Other, please describe:

**Does this PR introduce a breaking change?** (check one)

- [ ] Yes
- [x] No

If yes, please describe the impact and migration path for existing applications:

**The PR fulfills this requirement:**

- [x] It's submitted to the `dev` branch, _not_ the `main` branch

If adding a **new feature**, the PR's description includes:
- [x] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

**Other information:**


## Comments

### `@tobiu` commented on 2025-11-12T08:14:44Z

**Input from Gemini Pro:**

> ✦ Thank you for this excellent contribution! Adding the `update_issue_relationship` tool is a great enhancement that significantly improves our workflow for managing issue hierarchies.
> 
> ### What I Like:
> 
> *   **Great Enhancement:** This tool directly addresses the need to programmatically manage parent/child issue relationships, which was a key missing piece in our automation.
> *   **Clear API Design:** The changes to `openapi.yaml` are very well done. The tool's purpose, parameters, and documentation are clear and easy to understand.
> *   **Solid Implementation:** The core implementation is solid and the service logic is robust.
> 
> ### Follow-up Opportunities:
> 
> Based on this work, we've identified a few opportunities for further enhancements. We've created follow-up tickets for these, which you are more than welcome to pick up if you're interested:
> 
> *   **#7749:** Enhance the tool to support "Blocked By" and "Blocking" relationships.
> *   **#7750:** Improve the efficiency of the GraphQL mutations by minimizing their return payload.
> *   **#7751:** Refactor the `IssueSyncer` to remove redundant metadata from the markdown body.
> 
> ### Conclusion:
> 
> This is a fantastic addition to the project. I am approving this PR. Thank you again for your contribution!

---

