Bulk delete
Bulk delete clears selected rows from a lens in one action. Use it when trimming stale work, collapsing an obsolete program, or cleaning up after a bad import.
Deleting from Foundation is not the same as deleting in Jira — read the removal semantics below before you click.
Run a bulk delete
Section titled “Run a bulk delete”- Select the rows you want to remove (see Select rows).
- Press Delete or Backspace, or choose Delete selected from the select bar’s more menu.
- A confirmation dialog summarizes what’s about to happen, including descendant counts.
- Click Delete to confirm, or Cancel to back out.
What gets removed
Section titled “What gets removed”- Jira-backed rows are unlinked from the lens only. The underlying Jira issue is left alone, exactly the same as it was before you imported it.
- Flex Items (folders you created in Foundation) are deleted from the lens permanently — they don’t exist anywhere else.
- Children of deleted rows follow the same rules: linked issues get unlinked, Flex Items get removed.
This is the same distinction covered in Remove vs. delete.
Undoing a bulk delete
Section titled “Undoing a bulk delete”There is no direct undo. Instead:
- For Jira-backed rows, re-import them with Add from Jira or a Sync Agent. No data is lost — you’re just re-linking.
- For Flex Items, recreate them manually. Consider exporting the lens to CSV before any risky bulk delete so you have a record.
Safety tips
Section titled “Safety tips”- Expand the select bar before confirming to verify the count and status breakdown.
- Delete children first if you want to keep the parent — otherwise the confirmation bundles them together.
- For lenses many teams share, consider removing rather than deleting so someone else can restore if needed.
- If you hit a Jira permission error on a Flex Item, that usually means someone else converted it to a Jira issue (with Copy to Jira) and you no longer have edit rights.