Feat/fix fake responded statuses in audit stages patch#164
Merged
Suraiyya-786 merged 2 commits intoMay 26, 2026
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Added production-safe patch to correct incorrect Responded statuses
Converted fake Responded entries to No Response when no actual response or attachment exists
Added support for empty HTML rich text responses (
, etc.)Synced both child table (Audit Items) and legacy hardcoded fields
Replaced document save flow with direct frappe.db.set_value() updates to avoid validation failures during migration
Prevented accidental modification of genuine responded stages with attachments