Open jeanyang04 opened 1 week ago
Hello, thanks for reviewing our product! We get what you're pointing out, but we don't get how this is an issue - what is the expectation you have here, and how does it differ from our actual outcome?
Our belief is that the latest version of the product that is changed will be saved, which is instance B in your case. If instance A was to be saved but the user made changes on B last, that would be counter intuitive as well. Hence, we have to label this as an unclear issue as there isn't a clear expectation of what you are looking for!
Hope this clarifies your queries, thanks for testing our product!
Team chose [response.IssueUnclear
]
Reason for disagreement: Hi! Thanks for replying to my bug report. I understand that my initial submission may not have been as detailed as necessary, and I appreciate the feedback.
However, I'd like to clarify why I believe this issue impacts user experience and why the behavior may not meet user expectations.
While I didn’t explicitly state my expected behavior, it’s reasonable to assume users expect either:
As the app’s development team, I believe the team is best positioned to understand the implications of allowing multiple instances to modify the same data without conflict resolution. This is why I believed the issue would be apparent.
Here's some of the possible implications for reference:
I hope this can make the issue clearer, if not already. Thanks!
Summary
Multiple instances of the app are allowed, and the app will only prioritize the changes made on the last instance closed.
Steps to Reproduce
Screenshots