feat(cmdk): Add bulk issue actions to command palette#114278
Merged
Conversation
When issues are selected on the Issues feed, a new "N Selected Issues" group appears in the command palette with actions for resolve, archive, set priority, and assign to. The assign action shows all org members and teams as searchable sub-results. Fixes #65088 Fixes #61935 Co-Authored-By: Claude <noreply@anthropic.com>
github-actions
Bot
added
the
Scope: Frontend
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
rbro112
approved these changes
Apr 29, 2026
handleUpdate and handleBulkUpdate were nearly identical. Extract the shared logic into performBulkUpdate with an optional success callback.
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
Extract the duplicated issue list bulk update flow into shared helpers. Keep project selection and issue query invalidation behavior aligned between the actions bar and command palette so fixes only land in one place. Co-Authored-By: Codex <noreply@openai.com>
Pass the issue list query count through to the bulk command palette actions. The bulk action label and capped search copy depend on the total query match count, so keep the parent wiring in sync with the extracted bulk update helpers. Co-Authored-By: Codex <noreply@openai.com>
Add issue feed command palette actions for bulk updates when no issues are selected and keep the selected-issues actions available in the existing task slot. Reuse the shared bulk update path so command palette actions show a loader, and gate the bulk update actions behind confirmation prompts that explain the selected or query-wide scope before running. Co-Authored-By: OpenAI Codex <noreply@openai.com>
Contributor
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 7e75360. Configure here.
The "mark all" command palette actions rendered when no issues were
individually selected, causing getSelectedIds() to return an empty
array. Since [] is truthy in JS, paramsToQueryArgs produced {id: []}
instead of falling through to the query-based branch, silently
updating zero issues.
Thread an allInQuery flag through the update handlers so the "mark all"
path forces itemIds to undefined, which makes the API use the search
query to match all issues.
Comment on lines
+269
to
+271
| failSilently: true, | ||
| ...projectConstraints, | ||
| ...selection.datetime, |
Contributor
There was a problem hiding this comment.
Bug: Performing an "all-in-query" bulk action from the command palette results in a malformed success toast, like "Resolved ", because an empty itemIds array is passed to the notification handler.
Severity: LOW
Suggested Fix
The onActionTaken callback should differentiate between an empty selection and an all-in-query selection. Instead of passing itemIds ?? [], consider passing a special value or a flag to indicate an all-in-query action. Alternatively, update onIssueAction to check if the action was all-in-query and display a generic success message like "Resolved all issues in your query" instead of trying to list item IDs.
Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.
Location: static/app/views/issueList/actions/utils.tsx#L269-L271
Potential issue: When a user performs an "all-in-query" bulk update, such as "Mark all
issues as Resolved," from the command palette without any issues individually selected,
the `onActionTaken` callback is invoked with an empty array `[]` for `itemIds`. This
occurs because the `onSuccess` callback in `handleUpdate` defaults `undefined` `itemIds`
to an empty array. The `onIssueAction` handler is not designed for this scenario and
attempts to generate a success message by mapping over the empty `itemIds` array. This
results in an empty string for the issue's short ID, leading to a malformed toast
notification like "Resolved " with a trailing space and no issue identifier.
Also affects:
static/app/views/issueList/overview.tsx:949~951
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
2 participants
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
taskslot so it renders above the existing "Issues Feed" actionsCloses #65088
Closes #61935