I believe there was a bug where the ui allowed ZIP export in the org export screen, but I’m not currently involved in development of ZIP exports anymore. I’ll note that as of now, it is expected that this is unavailable for organizations.
1 Like
grb
June 6, 2025, 7:36pm
22
The following PRs by @djsmith85 were merged March 31–April 2. I don’t know if any of them are relevant to the behavior observed by @fham & @therave , but it illustrates that the new ZIP export function may still have a few “rough edges”:
main ← tools/pm-19656/fix-zip-option-not-being-set-correctly-after-navigating-to-AC
opened 07:51AM - 31 Mar 25 UTC
## 🎟️ Tracking
https://bitwarden.atlassian.net/browse/PM-19656
## 📔 Object… ive
QA defect: When the user navigates to the Admin console export and then navigates back to the password manager export, then the zip option is not displayed anymore.
The reason being that the changes to `vaultSelector` were happening before the subscription to it's changes were set up. Moving the subscription up within ngOnInit solves this.
## ⏰ Reminders before review
- Contributor guidelines followed
- All formatters and local linters executed and passed
- Written new unit and / or integration tests where applicable
- Protected functional changes with optionality (feature flags)
- Used internationalization (i18n) for all UI strings
- CI builds passed
- Communicated to DevOps any deployment requirements
- Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team
## 🦮 Reviewer guidelines
- 👍 (`:+1:`) or similar for great changes
- 📝 (`:memo:`) or ℹ️ (`:information_source:`) for notes or general info
- ❓ (`:question:`) for questions
- 🤔 (`:thinking:`) or 💭 (`:thought_balloon:`) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion
- 🎨 (`:art:`) for suggestions / improvements
- ❌ (`:x:`) or ⚠️ (`:warning:`) for more significant problems or concerns needing attention
- 🌱 (`:seedling:`) or ♻️ (`:recycle:`) for future improvements or indications of technical debt
- ⛏ (`:pick:`) for minor or nitpick changes
main ← tools/pm-19725/wrong-file-extension-when-exporting-with-attachments
opened 02:54PM - 31 Mar 25 UTC
## 🎟️ Tracking
https://bitwarden.atlassian.net/browse/PM-19725
## 📔 Object… ive
When exporting an individual vault with attachments it produces a json file and a folder with attachments. The export-file generated is a zip-file, but the file-extension was still using `.json`. This PR sets it to `.zip`
## ⏰ Reminders before review
- Contributor guidelines followed
- All formatters and local linters executed and passed
- Written new unit and / or integration tests where applicable
- Protected functional changes with optionality (feature flags)
- Used internationalization (i18n) for all UI strings
- CI builds passed
- Communicated to DevOps any deployment requirements
- Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team
## 🦮 Reviewer guidelines
- 👍 (`:+1:`) or similar for great changes
- 📝 (`:memo:`) or ℹ️ (`:information_source:`) for notes or general info
- ❓ (`:question:`) for questions
- 🤔 (`:thinking:`) or 💭 (`:thought_balloon:`) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion
- 🎨 (`:art:`) for suggestions / improvements
- ❌ (`:x:`) or ⚠️ (`:warning:`) for more significant problems or concerns needing attention
- 🌱 (`:seedling:`) or ♻️ (`:recycle:`) for future improvements or indications of technical debt
- ⛏ (`:pick:`) for minor or nitpick changes
main ← tools/pm-19775/export-scope-callout-not-updated-on-format-change
opened 09:56AM - 02 Apr 25 UTC
## 🎟️ Tracking
https://bitwarden.atlassian.net/browse/PM-19775
## 📔 Object… ive
The text within the export callout, wasn't set properly when switching between MyVault and an organization and back, as the filter only removed the zip-format option, but didn't set a new value.
## ⏰ Reminders before review
- Contributor guidelines followed
- All formatters and local linters executed and passed
- Written new unit and / or integration tests where applicable
- Protected functional changes with optionality (feature flags)
- Used internationalization (i18n) for all UI strings
- CI builds passed
- Communicated to DevOps any deployment requirements
- Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team
## 🦮 Reviewer guidelines
- 👍 (`:+1:`) or similar for great changes
- 📝 (`:memo:`) or ℹ️ (`:information_source:`) for notes or general info
- ❓ (`:question:`) for questions
- 🤔 (`:thinking:`) or 💭 (`:thought_balloon:`) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion
- 🎨 (`:art:`) for suggestions / improvements
- ❌ (`:x:`) or ⚠️ (`:warning:`) for more significant problems or concerns needing attention
- 🌱 (`:seedling:`) or ♻️ (`:recycle:`) for future improvements or indications of technical debt
- ⛏ (`:pick:`) for minor or nitpick changes