Case and collection downloads confirmed to have real ZIP and QKey format parity
Issue tracker claims case/collection downloads lack QKey format parity; claim found to be stale on independent verification
An internal issue tracker had flagged case and collection downloads as not format-parity clean since March 2026, claiming downloads were archive-only with no standalone structured export. Independent verification found this had already been resolved: both formats are genuinely built on demand from canonical database rows, not a static file reference, and the tracker entry was simply stale.
Root Cause
sourceArtifactService.js was rewritten at some point to build both zip (via real JSZip compression) and qkey (structured text export) artifacts per-request from live case/collection data, but the issue tracker documenting the original gap was never updated to reflect the fix.
Solution Steps
- No code fix was needed - the underlying capability was already correctly implemented.
- Update the stale issue tracker entry to Resolved status with the verification evidence, so future readers don't waste time re-investigating an already-fixed gap.
- Run the existing test covering both zip and qkey case bundle formats.
Validation
[object Object]
Rollback
[object Object]
Ecosystem: nodejs
License: CC-BY-4.0
Last updated: Jul 6, 2026