[GH-ISSUE #6802] [FR] Move or copy board item with content to different board #2998

Open
opened 2026-03-23 21:26:50 +00:00 by mirror · 5 comments
Owner

Originally created by @alyvusal on GitHub (Nov 16, 2024).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/6802

Description

We may need to move aaor do copy paste item with its content from one board to another board as it is related to new board mostly. It becomes pain to copy contents each time. Would be better we may just right click and move to desired board easily

Impact

I think it will be useful for anyone

Additional Context

No response

Originally created by @alyvusal on GitHub (Nov 16, 2024). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/6802 ### Description We may need to move aaor do copy paste item with its content from one board to another board as it is related to new board mostly. It becomes pain to copy contents each time. Would be better we may just right click and move to desired board easily ### Impact I think it will be useful for anyone ### Additional Context _No response_
Author
Owner

@annieappflowy commented on GitHub (Jan 3, 2025):

The target board will need to have the same schema. Otherwise, moved item may not match with your target board's property types.

<!-- gh-comment-id:2569268717 --> @annieappflowy commented on GitHub (Jan 3, 2025): The target board will need to have the same schema. Otherwise, moved item may not match with your target board's property types.
Author
Owner

@Rwang0316 commented on GitHub (Jun 26, 2025):

Closing this issue due to no response. If you’re still encountering the problem, please feel free to reopen or create a new issue with more details. Thanks!

<!-- gh-comment-id:3006945037 --> @Rwang0316 commented on GitHub (Jun 26, 2025): Closing this issue due to no response. If you’re still encountering the problem, please feel free to reopen or create a new issue with more details. Thanks!
Author
Owner

@alyvusal commented on GitHub (Jun 26, 2025):

The target board will need to have the same schema. Otherwise, moved item may not match with your target board's property types.

During move unmatched field could be shown to user to select which one to keep

<!-- gh-comment-id:3007708301 --> @alyvusal commented on GitHub (Jun 26, 2025): > The target board will need to have the same schema. Otherwise, moved item may not match with your target board's property types. During move unmatched field could be shown to user to select which one to keep
Author
Owner

@alyvusal commented on GitHub (Jun 26, 2025):

Closing this issue due to no response. If you’re still encountering the problem, please feel free to reopen or create a new issue with more details. Thanks!

It is not issue, it is feature request and AFAIK this feature not implemented yet. Why you close it?! Does it make sense to close not implemented FR and reopen or create new ones again ?

<!-- gh-comment-id:3007715094 --> @alyvusal commented on GitHub (Jun 26, 2025): > Closing this issue due to no response. If you’re still encountering the problem, please feel free to reopen or create a new issue with more details. Thanks! It is not issue, it is feature request and AFAIK this feature not implemented yet. Why you close it?! Does it make sense to close not implemented FR and reopen or create new ones again ?
Author
Owner

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

Closing this issue due to no response. If you’re still encountering the problem, please feel free to reopen or create a new issue with more details. Thanks!

It is not issue, it is feature request and AFAIK this feature not implemented yet. Why you close it?! Does it make sense to close not implemented FR and reopen or create new ones again ?

Sorry, it was a mistake by our intern. I have reopened it.

<!-- gh-comment-id:3007774217 --> @annieappflowy commented on GitHub (Jun 26, 2025): > > Closing this issue due to no response. If you’re still encountering the problem, please feel free to reopen or create a new issue with more details. Thanks! > > It is not issue, it is feature request and AFAIK this feature not implemented yet. Why you close it?! Does it make sense to close not implemented FR and reopen or create new ones again ? Sorry, it was a mistake by our intern. I have reopened it.
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#2998
No description provided.