Repository navigation
feat(issue): add related, add-related and remove-related commands - #172
Open
lollipop-onl wants to merge 2 commits into
Open
lollipop-onl wants to merge 2 commits into
lollipop-onl wants to merge 2 commits into
Conversation
This was referenced Sep 28, 2026
Backlog added related issues, and backlog-js already wraps the endpoints, but bee only reached them through `bee api`. That path needs the target's numeric issue ID rather than its key, which agents and users kept getting wrong. The commands accept issue keys or IDs for both sides and resolve targets one at a time, reporting each as it lands, so a failure part-way through still shows which relations were already changed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Trying the commands against a real space showed three problems. A target key that did not exist failed only after the earlier targets had already been related, leaving the change half-applied. Relating an issue to itself returns 200 without doing anything, so bee reported a relation that was never made. And a target given by ID was echoed back as a bare number, although both endpoints return the target issue and its key. Every target (and, for add-related, the base issue) is now resolved up front, self-relations are rejected before any write, and success messages use the key from the response. `resolveIssueId` also matches `star add` in only treating plain digits as IDs, and the CLI tests now mock it at the package boundary instead of re-testing it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
lollipop-onl
force-pushed
the
lollipop-onl/feat-issue-related
branch
from
September 28, 2026 17:43
8cd542f to
1a22cca
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds commands for related issues. backlog-js already wraps the endpoints, but bee only reached them through
bee api, which needs the target's numeric issue ID rather than its key.bee issue related <issue>GET /issues/:issueIdOrKey/relatedIssuesbee issue add-related <issue> <targets...>POST /issues/:issueIdOrKey/relatedIssues(targetIssueId)bee issue remove-related <issue> <targets...>DELETE /issues/:issueIdOrKey/relatedIssues/:relatedIssueIdresolveIssueIdin@repo/backlog-utilsuses numeric input as-is and otherwise looks it up withgetIssue(), next toresolveUserId/resolveProjectIds.--jsonprints the responses instead.:relatedIssueIdis the target's ID. The public reference does not say either; both were confirmed on a live space and against the server implementation.project users/add-user/remove-useranddocument add-tag/remove-tag(feat(document): add comments, count, add-tag and remove-tag commands #170).Test plan
vp checkpassesvp test: all tests pass, includingresolve-issue.test.tsand the three command testsvp run --filter @nulab/bee generate:skill:checkpasses🤖 Generated with Claude Code