"As a technical project manager, I rely heavily on the task description field to document architectural changes and project requirements.
Currently, the auto-save feature is very helpful for data persistence, but it lacks a ‘commit’ mechanism to notify the team that an edit session is complete. Since there is no ‘Save’ button, I often have to navigate away from the task to trigger a save or rely on implicit system behavior, which can be confusing for team members expecting a notification of a final update.
My Proposal: I suggest adding a manual ‘Save’ button for task descriptions that remains optional.
-
Auto-save would continue to function in the background for safety.
-
The ‘Save’ button would serve as a trigger to finalize the update and notify relevant stakeholders/collaborators that the changes are ready for review.
This would give us better control over when notifications are sent, prevent notification spamming for minor corrections, and ensure that team members only receive alerts when a substantial update is finalized.
I believe this enhancement would significantly improve the workflow for teams that manage complex documentation within tasks. Thank you for considering this improvement."