Skip to content

Ticket boards: GitHub "Take issues labelled" can be set to none, to take every open issue - #211

Merged
devileya merged 1 commit into
masterfrom
devileya/210-ticket-boards-github-take-issues-labelled-ca
Nov 20, 2026
Merged

devileya merged 1 commit into
masterfrom
devileya/210-ticket-boards-github-take-issues-labelled-ca

Conversation

@devileya

Copy link
Copy Markdown
Collaborator

Summary

  • GitHub boards: Take issues labelled gets a first option, Any open issue (no label needed), for repositories where nobody labels issues. It's saved as pickAny on the board (tickets/mod.rs Board::pick_any, takes_any, pick_column). It's GitHub only: saving clears it on other trackers. Existing boards keep their label.
  • Listing (tickets/github.rs gh_list): open issues without the labels filter, still with state=open, the assignee setting, oldest first and MAX_ISSUES. Pull requests and issues that have one of the board's state labels are left out.
  • Who may start a run (github::ready): with no label, the watch checks the issue's author. It takes the issue only if the author can write to the repository (can_write) or is on the allowlist, and the issue was opened after the board was made. Others stay listed and are sent to the agent by hand. Blockers, max_per_run, worktrees and parallel runs are unchanged.
  • Running again: an issue the agent already worked on runs again when someone who may write takes off the state label it was left with, after its last run ended (gh_unlabeled, asked_again). Taking off the working label doesn't count, because DevCat removes it itself at the end of each run.
  • Comments (worker.rs run comment and no-pull-request note, recover.rs, the not-planned comment in github.rs) say "remove the label X (or send it to the agent in DevCat)" instead of naming a trigger label (github::run_again).
  • Watch loop, check_column, to_queue and the agent tools (agent_tools/workspace.rs) use Board::pick_column(), so an "any" board is watched and listed.
  • UI: the option and its explanation in BoardDialog.tsx. "Also take issues from" replaces "Also take labels from" when the option is on. "Any open issue" shows in the board list, the toolbar and the column picker (TicketsTab.tsx, TicketsPanel.tsx, api.ts pickName).
  • Docs: site/docs/pages/github-board.md (new section "Any open issue, without a label"), site/docs/pages/tickets.md, and a CHANGELOG line under Unreleased.

Test plan

  • cargo check / cargo test --lib (src-tauri): new tests github::tests::any_open_issue (mock GitHub with an issue without labels, a pull request, an issue with a state label, a stranger's issue, an issue from before the board, and re-asks by a writer, by DevCat on the working label and by a stranger) and older_boards_keep_their_label
  • tsc (desktop)
  • Manual: set a GitHub board to "Any open issue". Check that the list leaves out pull requests and issues with state labels, that the watch takes a writer's new issue but not a stranger's, and that removing needs-info as a writer runs the issue again

Notes

  • Security: this widens what can start an unattended run, from "someone trusted added the label" to "someone trusted opened the issue". The issue text is outside input either way (Scope::unattended, trusted comments only), so the agent's limits are the same.
  • Side effect to review: reopening an issue whose pull request was merged runs it again at the next check. When the merge closed it, DevCat took agent-review off, and that counts as asking again. Only people with write access can reopen an issue DevCat closed. This is written in the docs.
  • None of this has been compiled or run yet: the checks above are still to do.

How it was checked

  1. Run cargo test --lib tickets in src-tauri. The new tests are github::tests::any_open_issue and older_boards_keep_their_label; the existing GitHub board tests should still pass.
  2. Run tsc for the desktop app.
  3. Manual: connect a GitHub board and set "Take issues labelled" to "Any open issue (no label needed)". Check the text under the field and that "Also take labels from" is renamed "Also take issues from". Save it.
  4. In the Tickets tab, the list shows "Any open issue": open issues with or without labels, but no pull requests and no issues labelled agent-working, agent-review, needs-info, ready-for-human or wontfix.
  5. Turn Watch on. As someone with write access, open a new issue assigned as the board says: the next check takes it. Open one from an account without write access: it stays in the list and starts only with "Fix with the agent". Issues opened before the board was made are not taken by the watch.
  6. After a run that ends in needs-info, check that the comment says to remove the needs-info label. Remove it as a writer: the next check runs the issue again on the same branch.
  7. Edit an older board that has a trigger label: it still shows its label and works as before.

Closes #210

Opened by the DevCat agent.

…, to take every open issue

GitHub boards can now take any open issue. "Take issues labelled" has a new first option, "Any open issue (no label needed)". It's saved as an explicit Board::pick_any, so an older board missing its label is not read as "any". Saving clears it on Jira, Trello and Linear boards, and existing boards keep their label.

Listing: the board asks GitHub for open issues without the labels filter. State, assignee, oldest-first order and MAX_ISSUES stay. Pull requests are left out, and so are issues that have one of the board's state labels.

Who may start a run: github::ready now checks who opened the issue, since there's no label to go by. The watch takes an issue only if its author can write to the repository (can_write) or is on the allowlist, and only if it was opened after the board was made. Blockers, max_per_run, worktrees and parallel runs work as before.

Running again: an issue the agent already worked on runs again only when someone who may write takes off the state label it was left with, after its last run ended. Taking off the working label doesn't count, because DevCat removes that one itself at the end of every run.

Comments: DevCat's comments (needs info, failed, no pull request, crash recovery, closed as not planned) now say "remove the label `X` (or send it to the agent in DevCat)" instead of naming a trigger label.

The dialog explains the rule under the field. With the new option, the allowlist field is renamed "Also take issues from". The board list, toolbar and agent tools show "Any open issue". Docs (github-board.md, tickets.md) and the CHANGELOG are updated.

One side effect a reviewer should know about: if someone reopens an issue whose pull request was merged, it runs again. When the merge closed it, DevCat took agent-review off, and that counts as asking again. Only people with write access can reopen an issue DevCat closed. This is written in the docs.

I couldn't run anything here: no cargo check, cargo test or tsc. All checks so far are from reading the code.

#210
Worked on by the DevCat agent.
@devileya
devileya marked this pull request as ready for review November 20, 2026 05:14
@devileya
devileya merged commit d6abf80 into master Nov 20, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Ticket boards: GitHub "Take issues labelled" can be set to none, to take every open issue

1 participant