[GH-ISSUE #8376] bug in the Grid feature #3778

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

Originally created by @MasoudKhanalizadeh on GitHub (Dec 4, 2025).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/8376

Bug Description

Hi Developers,

I’ve found a bug in the Grid feature. I created a Grid for my to-do list, and when I duplicated it, any changes I made in the duplicated Grid were also applied to the original Grid it was copied from.

How to Reproduce

Create a new Grid.

Add some sample fields and rows.

Duplicate the Grid.

Edit any field, property, or row in the duplicated Grid.

Observe that the same changes also appear in the original Grid.

Expected Behavior

The duplicated Grid should be a completely independent copy.
Changes made in the duplicated Grid should not affect the original Grid, and edits to the original should not affect the duplicate.

Operating System

windows 11

AppFlowy Version(s)

0.10.5 (official build)

Screenshots

No response

Additional Context

No response

Originally created by @MasoudKhanalizadeh on GitHub (Dec 4, 2025). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/8376 ### Bug Description Hi Developers, I’ve found a bug in the Grid feature. I created a Grid for my to-do list, and when I duplicated it, any changes I made in the duplicated Grid were also applied to the original Grid it was copied from. ### How to Reproduce Create a new Grid. Add some sample fields and rows. Duplicate the Grid. Edit any field, property, or row in the duplicated Grid. Observe that the same changes also appear in the original Grid. ### Expected Behavior The duplicated Grid should be a completely independent copy. Changes made in the duplicated Grid should not affect the original Grid, and edits to the original should not affect the duplicate. ### Operating System windows 11 ### AppFlowy Version(s) 0.10.5 (official build) ### Screenshots _No response_ ### Additional Context _No response_
Author
Owner

@LucasXu0 commented on GitHub (Dec 5, 2025):

Thanks for reporting this issue. We can reproduce it and will include the bug fix in the upcoming release.

<!-- gh-comment-id:3615068149 --> @LucasXu0 commented on GitHub (Dec 5, 2025): Thanks for reporting this issue. We can reproduce it and will include the bug fix in the upcoming release.
Author
Owner

@MasoudKhanalizadeh commented on GitHub (Dec 10, 2025):

Dear Lucas,

Your welcome.Thank you for your useful application

best regards

On Fri, Dec 5, 2025, 6:04 AM Lucas @.***> wrote:

LucasXu0 left a comment (AppFlowy-IO/AppFlowy#8376)
https://github.com/AppFlowy-IO/AppFlowy/issues/8376#issuecomment-3615068149

Thanks for reporting this issue. We can reproduce it and will include the
bug fix in the upcoming release.


Reply to this email directly, view it on GitHub
https://github.com/AppFlowy-IO/AppFlowy/issues/8376#issuecomment-3615068149,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BDAEL6QGETI534MXH7ODQAL4ADVJRAVCNFSM6AAAAACOASYRNCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMMJVGA3DQMJUHE
.
You are receiving this because you authored the thread.Message ID:
@.***>

<!-- gh-comment-id:3637032657 --> @MasoudKhanalizadeh commented on GitHub (Dec 10, 2025): Dear Lucas, Your welcome.Thank you for your useful application best regards On Fri, Dec 5, 2025, 6:04 AM Lucas ***@***.***> wrote: > *LucasXu0* left a comment (AppFlowy-IO/AppFlowy#8376) > <https://github.com/AppFlowy-IO/AppFlowy/issues/8376#issuecomment-3615068149> > > Thanks for reporting this issue. We can reproduce it and will include the > bug fix in the upcoming release. > > — > Reply to this email directly, view it on GitHub > <https://github.com/AppFlowy-IO/AppFlowy/issues/8376#issuecomment-3615068149>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/BDAEL6QGETI534MXH7ODQAL4ADVJRAVCNFSM6AAAAACOASYRNCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMMJVGA3DQMJUHE> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >
Author
Owner

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

This issue was fixed. I am closing this issue.

<!-- gh-comment-id:3663141949 --> @appflowy commented on GitHub (Dec 17, 2025): This issue was fixed. I am closing this issue.
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#3778
No description provided.