Repository navigation
Ticket boards: GitHub "Take issues labelled" can be set to none, to take every open issue - #211
Merged
devileya merged 1 commit intoNov 20, 2026
Conversation
…, 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.
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
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
pickAnyon the board (tickets/mod.rsBoard::pick_any,takes_any,pick_column). It's GitHub only: saving clears it on other trackers. Existing boards keep their label.tickets/github.rsgh_list): open issues without thelabelsfilter, still withstate=open, the assignee setting, oldest first andMAX_ISSUES. Pull requests and issues that have one of the board's state labels are left out.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.gh_unlabeled,asked_again). Taking off the working label doesn't count, because DevCat removes it itself at the end of each run.worker.rsrun comment and no-pull-request note,recover.rs, the not-planned comment ingithub.rs) say "remove the labelX(or send it to the agent in DevCat)" instead of naming a trigger label (github::run_again).check_column,to_queueand the agent tools (agent_tools/workspace.rs) useBoard::pick_column(), so an "any" board is watched and listed.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.tspickName).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 testsgithub::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) andolder_boards_keep_their_labeltsc(desktop)needs-infoas a writer runs the issue againNotes
Scope::unattended, trusted comments only), so the agent's limits are the same.agent-reviewoff, and that counts as asking again. Only people with write access can reopen an issue DevCat closed. This is written in the docs.How it was checked
cargo test --lib ticketsin 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.tscfor the desktop app.needs-infolabel. Remove it as a writer: the next check runs the issue again on the same branch.Closes #210
Opened by the DevCat agent.