Skip to content

🐛 Scanner decomposition files child issues in the parent's repo instead of the managed repo where the work lives #18680

Closed

Description

@clubanderson

Problem

When the scanner decomposes a tracker, it files every child issue in the parent's repo, even when the work belongs in another repo the hive manages.

Seen 2026-11-17: the scanner decomposed #18596 at 08:00 and filed #18660 (Windows capture) and #18661 (Linux capture) in hivecommons/hive. All of that code lives in hivecommons/quorum-companion. The scanner knew this; the #18660 body says:

The work lives in hivecommons/quorum-companion; this child keeps the #18596 "Next" checklist actionable. Move or mirror it there if preferred.

The children are linked to the parent with "Part of #18596" and <!-- hive:parent 18596 -->. Both use a bare number, which resolves only within the same repo, so a child in another repo would lose the parent link. As a result:

Expected

  • Decomposition files each child in the managed repo where its work lives, determined from the target paths and repo named in the plan.
  • The parent link is cross-repo: Part of hivecommons/hive#18596 and a hive:parent marker carrying owner/repo#N.
  • The parent's tracker count and checklist (e.g. "tracker 0/3") count children in any managed repo.
  • Children are still never filed in unmanaged repos.

Acceptance

  • A test where a plan names another managed repo → the child is created there with the full-form parent ref.
  • A test where the tracker progress counts a closed cross-repo child.
  • A test that an unmanaged repo falls back to the parent's repo.
  • changelog.d fragment.

Related: #18676 (cross-repo PR → issue stage link), #18675.

Activity

  1. added
    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
    on Nov 17, 2026
  2. self-assigned this
    on Nov 17, 2026
  3. clubanderson commented on Nov 17, 2026

    @clubanderson
    MemberAuthor

    Claimed: an operator-dispatched agent is working on this now. Hive agents, please do not pick it up.

  4. hivecommons-hive commented on Nov 17, 2026

    @hivecommons-hive
    Contributor

    Thanks for filing this issue! To help us reproduce and investigate, could you please include the commit SHA of the build you're running?

    You can find it by running:

    git rev-parse --short HEAD
    

    Or check the bottom of the console UI for the version string.

    This issue will be on hold until a SHA is provided. Simply add a comment with the SHA and the label will be automatically removed.

  5. added a commit that references this issue on Nov 17, 2026
    915446a
  6. added a commit that references this issue on Nov 17, 2026
    cc6847d
  7. clubanderson commented on Nov 17, 2026

    @clubanderson
    MemberAuthor

    Closed by #18688 (merged as ef8a7fc). Scanner decomposition now files each child in the managed repo where its work lives, linked to the parent as Part of owner/repo#N with a <!-- hive:parent owner/repo#N --> marker. Tracker progress and the decomposed-parent close count children in any managed repo, and an unmanaged child repo falls back to the parent's repo.

  8. added a commit that references this issue on Nov 18, 2026
    218f444
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/bugCategorizes issue or PR as related to a bug.needs-shatriage/acceptedIndicates an issue or PR is ready to be actively worked on.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions