Description
Issue: Data Loss Due to Browser Cache Conflict in Multi-Browser Scenario
Description
When working with issues across multiple browsers, I encountered a data loss problem. After making updates in one browser and then returning to another browser where the issue was previously loaded, the system overwrote the newer changes with cached data from the first browser.
Steps to Reproduce
- Open an issue in Browser A
- Switch to Browser B and open the same issue
- Make substantial updates to the issue in Browser B
- After some time, return to Browser A and load the same issue
- The system automatically saves the cached (outdated) version from Browser A, overwriting the updates made in Browser B
Observed Behavior
When returning to Browser A, the system performs an "auto save" of the cached content, overwriting the newer updates made in Browser B. This can be verified in the Activity log, which shows that the older cached content was saved over the newer content.
Expected Behavior
The system should detect that there are newer changes to the issue and either:
- Load the most recent version of the issue data
- Warn the user about the conflict and provide options to resolve it
- Prevent auto-saving of outdated cached content
Impact
This bug causes significant data loss. While it's possible to restore the content through the Activity log, it requires substantial effort to recover the lost updates.
Environment
- Self-hosted Huly Platform
- Multiple browsers (Safari iPad, Chrome MacOS)
Additional Information
The Activity log confirms this is happening - it shows that cached content from Browser A was auto-saved after updates were made in Browser B.