You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are some issues with the descriptions. They change immediately while we are typing, which is not a good experience as it results in unattended changes without any log of the previous version. It would be a better experience if we had a “save button” for descriptions. After clicking save, Plane should automatically create a new comment with the updated description content as the logged-in user.
Why should this be worked on?
This issue should be addressed because it significantly impacts the user experience. When descriptions change immediately as users type, it can lead to unintended modifications without any record of the previous versions. This lack of version control can cause confusion and errors, making it difficult to track changes and maintain accurate documentation.
Implementing a “save button” for descriptions would provide a more controlled and reliable way to update content. By creating a new comment with the updated description upon saving, users can have a clear log of changes, enhancing transparency and accountability. This improvement would ensure that all modifications are intentional and properly documented, leading to a more efficient and user-friendly system.
The text was updated successfully, but these errors were encountered:
Hi there! I can confirm this happens every time someone simply views an issue, causing the "Activity" portion of the issue to be congested with unnecessary logging:
Is there an existing issue for this?
Summary
Hi Plane Team,
There are some issues with the descriptions. They change immediately while we are typing, which is not a good experience as it results in unattended changes without any log of the previous version. It would be a better experience if we had a “save button” for descriptions. After clicking save, Plane should automatically create a new comment with the updated description content as the logged-in user.
Why should this be worked on?
This issue should be addressed because it significantly impacts the user experience. When descriptions change immediately as users type, it can lead to unintended modifications without any record of the previous versions. This lack of version control can cause confusion and errors, making it difficult to track changes and maintain accurate documentation.
Implementing a “save button” for descriptions would provide a more controlled and reliable way to update content. By creating a new comment with the updated description upon saving, users can have a clear log of changes, enhancing transparency and accountability. This improvement would ensure that all modifications are intentional and properly documented, leading to a more efficient and user-friendly system.
The text was updated successfully, but these errors were encountered: