[feature]: safe issue description from changes

[yiiman-dev]

Is there an existing issue for this?

• I have searched the existing issues

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.

[sypion]

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:

[GauthierPLM]

I experienced the same thing and went with hiding the activity. When I need to write one, I write it elsewhere before copy/pasting the content.

Other platforms will keep only one event for the same edit process. I would expect Plane to do the same.

[vihar]

Thank you all for the detailed feedback! We take these UX concerns seriously and will address them with high priority. Let me break down our planned actions:

• Regarding the description saving behavior: We understand the current auto-save functionality is causing unintended changes. We'll implement a hybrid approach allowing users to choose between manual save (with a save button) and auto-save modes. This will give users more control while maintaining flexibility.
• For issue activity logging: We'll optimize the activity log by collapsing repeated actions and implementing smarter grouping of similar activities. This should significantly reduce the noise in the activity feed.

@GauthierPLM - Could you elaborate on your workaround of "hiding the description"? Understanding your specific use case would help us design a better solution.

Is anyone able to share screen recordings of these issues? It would help us better understand the exact scenarios and implement more precise fixes.

Thank you for helping us improve Plane! We'll prioritize these changes in our next Cycle.

[GauthierPLM]

Hi @vihar

I want to come back at what I mentioned earlier since I updated my Plane instance. I tested the behavior and confirm that multiple edits from the same person do not trigger multiple times the description. Instead, if the last edit was on the description, the timestamp of it is instead updated.

On the "hiding the description", it was a typo on my side: I intended to say I hide the activity updates.

Sorry for the disturbance. :)