Select and bulk-update Issues
Select visible Issues and apply supported property or lifecycle changes as one authorized batch.
Team Issues, My Issues, and Feature Issue tables support session-only row selection for daily triage and cleanup.
Archived Issues and Deleted Issues also provide row/header checkboxes and the shared Actions toolbar. Ctrl-click (Cmd-click on macOS) a row to toggle its selection; Shift-click a checkbox or row to select a visible range. Their actions are limited to lifecycle changes: Unarchive/Delete for archived rows and Restore/Permanently delete for deleted rows.
Select Issues
- Select a row with its checkbox.
- Ctrl-click a row body (Cmd-click on macOS) to toggle only that Issue while preserving the rest of the selection.
- Shift-click a checkbox or row body to select the visible range.
- Use the header checkbox to select or clear the currently visible rows.
- Grouped tables exclude collapsed groups from the visible range.
- Changing the table scope or hiding rows prunes selection; changing the table identity clears it.
Selection is not saved to URLs, saved views, default views, local drafts, or server state. Press Escape to close an open Actions panel; when the panel is already closed, Escape clears the current selection. Editable fields keep their own Escape behavior.
Direct-shared or read-only Issues can remain selected so the selection stays honest, but bulk commands are unavailable unless every selected Issue is editable, active, and compatible with the command.
Apply a bulk action
Open Actions after selecting one or more Issues. The panel searches only commands backed by existing Issue mutations:
- Status
- Priority
- Assignee
- Labels
- Primary Feature
- Feature Phase
- Due date
- Estimate
- Create related
- Mark as
- Remove relations
- Recoverable delete
Commands are available only when the whole selection passes permission, lifecycle, and option-compatibility checks. Mixed Team selections show only compatible options, and a denied row never gets silently skipped in favor of a partial update.
Bulk execution uses one server-authorized batch operation. Phase assignment requires every selected Issue to belong to the same Feature and writes one aggregate Feature Activity event per affected Feature while preserving per-Issue audit evidence. Quiet property changes use optimistic cache updates with rollback. Relationship and hierarchy actions apply server-confirmed results immediately, then retain background cache and realtime reconciliation. Activity, audit, notifications, and private realtime updates otherwise remain per Issue and follow the corresponding single-Issue mutation contract.
Create or connect related work
Create related can create one Issue connected to every selected Issue or one parent above the whole selection. It also supports creating one Issue that is blocked by—or blocks—the selection. Bulk sub-issue creation is intentionally not offered here; create sub-issues from an individual Issue instead.
For Parent issue..., the create dialog shows the same Sub-issues card used when starting from one Issue. Every selected Issue appears as a separate row with its status, key, title, property controls, and remove action. You can also use Add sub-issue to draft more children. The count includes both the selected Issues and added drafts. Removing a selected row excludes it from the parent operation; the remaining selected Issues are still moved beneath the new parent in one batch.
If an added draft child cannot be confirmed after the new parent is created, only that unresolved draft remains with its attachments. Use Retry sub-issues to finish it without recreating the parent, or explicitly remove or cancel the draft to discard it.
When the create dialog opens for a related Issue, the relation appears as the same square-and-flag property badge used by Add related issue... in the ellipsis menu. Select the badge to review the related Issues by status, key, and title. Use the X beside a source to remove it from the pending relationship. Use Add related issue... in the ellipsis menu to append more Issues to the same badge; Issues already in the draft are omitted from the picker. The remaining sources are still submitted as one batch; removing every source turns the dialog into an ordinary Issue create.
Mark as connects the selection to one existing active Issue in the same Team. Available actions include Sub-issue of..., Related to..., Blocked by..., Blocking..., and Duplicate of.... Parent of... appears only when one Issue is selected. The target picker omits the selected Issues, inaccessible or inactive Issues, cross-Team Issues, and hierarchy choices that would create a cycle.
Choosing any existing-target action replaces the same command palette with the eligible Issue list. Choosing an Issue then replaces that list with a compact review in the same panel—without opening a larger modal. Back returns to the previous palette stage, and Cancel closes the palette without clearing the selection.
Before applying the action, the review summarizes the direction, Issue count, target, and effects such as reparenting, Duplicate status, or a blocked Issue moving to Backlog. The complete selection succeeds or nothing changes.
Use Remove relations when the selection already contains hierarchy, relationship, dependency, or duplicate links. You can remove parents, choose one linked Related to, Blocked by, or Blocking target, or unmark duplicates. The same palette shows how many selected Issues are affected before you confirm; selected Issues without that relationship remain unchanged. Removing a blocker does not change Issue status. Unmarking a duplicate restores its previous active status when available, otherwise the Team default.
Privacy and agent boundaries
Selection counts and Issue references remain display-safe. Private Team names, hidden labels, assignees, Features, estimate settings, and raw Issue UUIDs are not exposed through the toolbar, command panel, errors, Activity, notifications, exports, or agent payloads.
Integrity can explain a selection or draft a proposed batch action, but it does not apply a bulk mutation without an explicit user action.