Story (Required)

As a User trying to correct or refine previous feedback I want to be able to edit my existing comment or prevent a new one from being created on subsequent actions

This epic addresses the user friction and system clutter caused by creating a new, often duplicate, comment every time a specific action is performed, such as "completing" an item. By allowing users to update their existing comment (if one exists) or suppressing new comments on repeat actions, we improve the customer's experience by keeping threads clean and focused.

Background (Required)

Currently, when a user performs a certain action (e.g., clicking the "Complete" button/action on an item, or a similar state transition), the system automatically generates a new, often generic, comment. If the user performs this action multiple times, or reverses and re-performs the action, a chain of duplicate or near-duplicate comments is created. This leads to comment thread bloat, making it difficult to follow actual discussion or unique feedback. The core problem is the creation of a new comment rather than the update of an existing one or the suppression of new comments when the existing state-based comment is already present.

Out of scope

• The ability to edit comments made by other users (focus is on self-editing).
• A complete overhaul of the comment section UI/UX.
• Allowing full rich-text formatting in the comments (unless already supported).

• Approach (Required)

The general approach will be to check for an existing comment by the current user specific to the triggering action (e.g., the "Completion" action).

1. Identify the Trigger: Determine the action(s) that currently generate an automatic comment and target that code path.
2. Check for Existing Comment: Before creating a new comment, check if the current user already has a comment associated with that specific state or action on the current item.
3. Conditional Logic: if an existing, matching comment is found, update the content/timestamp of that existing comment instead of creating a new one. The updated content should reflect the current state/
.