Bulk edit
Bulk edit changes one field across every selected row in a single pass. Use it when you reassign a chunk of work, mark a batch as blocked, or roll priorities on a whole program.
Every bulk edit goes through the standard Jira API, so your Jira workflows, permission schemes, and notifications still apply.
Change priority in bulk
Section titled “Change priority in bulk”- Select two or more rows (see Select rows).
- In the select bar, click Change priority.
- Pick a priority from the dropdown — Highest, High, Medium, Low, Lowest.
- Foundation updates each selected issue and shows a success toast with the count.
Change status in bulk
Section titled “Change status in bulk”Status changes need a valid workflow transition for each issue. Because different issue types can have different transitions, bulk status changes are handled row-by-row:
- Select your rows.
- Click Change status in the select bar.
- Use the inline hint to open each row’s Status cell and pick the transition. The status editor shows only the transitions actually available for that issue.
This avoids half-applied transitions when some issues have a target status others don’t.
Change assignee in bulk
Section titled “Change assignee in bulk”Assignee changes require an Atlassian account ID, so Foundation routes them through the per-row editor for safety:
- Select your rows.
- Click Change assignee in the select bar.
- Open each row’s Assignee cell and pick the person. Typeahead searches every user who can access your Jira site.
What bulk edit respects
Section titled “What bulk edit respects”- Jira permissions — if you can’t edit an issue in Jira, Foundation won’t let you update it from the select bar either.
- Issue cache — every update refreshes the local cache so the grid reflects the new value right away.
- Other viewers — teammates looking at the same lens see the change when they refresh.
- Expand the select bar (chevron) to see metric cards before you commit — you’ll catch cases where the selection isn’t what you thought.
- Use Shift + C to pull in every child of a selected parent, then bulk-edit the whole subtree.
- If an update fails (workflow rule, validator), the toast tells you how many succeeded and how many were rejected.