[GH-ISSUE #7769] [Bug] Changing any field in a sorted Grid removes the modified row from proper sort order #3425

Closed
opened 2026-03-23 21:30:03 +00:00 by mirror · 3 comments
Owner

Originally created by @rockerest on GitHub (Apr 17, 2025).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/7769

Originally assigned to: @appflowy on GitHub.

Bug Description

Basically as the title says: If a Grid is sorted, changing any field in a row - even if that field is not part of the sort - removes the row from proper sort order and places it at the bottom of the Grid.

How to Reproduce

  1. Create a Grid
  2. Add some data (at least 2 rows will be necessary to see this in effect)
  3. Add a sort to the Grid
  4. Modify the first row, changing a field that is not part of the applied sort
  5. Note the field is placed at the bottom of the Grid

Expected Behavior

  1. Changing a field should always properly apply the correct sorts and filters
  2. Changing a field that is not part of any sort or filter in the current view should have no effect

Operating System

Windows

AppFlowy Version(s)

0.8.8

Screenshots

https://github.com/user-attachments/assets/7d39f2ee-c7d0-4e8b-acb0-484c1bd10ab9

Additional Context

No response

Originally created by @rockerest on GitHub (Apr 17, 2025). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/7769 Originally assigned to: @appflowy on GitHub. ### Bug Description Basically as the title says: If a Grid is sorted, changing **any** field in a row - even if that field is not part of the sort - removes the row from proper sort order and places it at the bottom of the Grid. ### How to Reproduce 1. Create a Grid 2. Add some data (at least 2 rows will be necessary to see this in effect) 3. Add a sort to the Grid 4. Modify the first row, changing a field that is not part of the applied sort 5. Note the field is placed at the bottom of the Grid ### Expected Behavior 1. Changing a field should always properly apply the correct sorts and filters 2. Changing a field that is not part of any sort or filter in the current view should have no effect ### Operating System Windows ### AppFlowy Version(s) 0.8.8 ### Screenshots https://github.com/user-attachments/assets/7d39f2ee-c7d0-4e8b-acb0-484c1bd10ab9 ### Additional Context _No response_
mirror 2026-03-23 21:30:03 +00:00
Author
Owner

@bogdanpc28 commented on GitHub (May 6, 2025):

I was just going to create the same bug. it's really annoying and it's a basic functionality for a grid that can ruin other features of it if it's not fixed in time.

<!-- gh-comment-id:2853692502 --> @bogdanpc28 commented on GitHub (May 6, 2025): I was just going to create the same bug. it's really annoying and it's a basic functionality for a grid that can ruin other features of it if it's not fixed in time.
Author
Owner

@annieappflowy commented on GitHub (Jun 15, 2025):

The web app doesn't have this issue.

<!-- gh-comment-id:2973513346 --> @annieappflowy commented on GitHub (Jun 15, 2025): The web app doesn't have this issue.
Author
Owner

@appflowy commented on GitHub (Dec 22, 2025):

Fixed in the upcoming release (v0.10.8)

<!-- gh-comment-id:3679967296 --> @appflowy commented on GitHub (Dec 22, 2025): Fixed in the upcoming release (v0.10.8)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
AppFlowy-IO/AppFlowy#3425
No description provided.