[GH-ISSUE #8569] [FR] Apply a template to a database record #3913

New issue

Open

opened 2026-03-23 21:34:06 +00:00 by mirror · 3 comments

mirror commented

2026-03-23 21:34:06 +00:00

Owner

Originally created by @Ray0m on GitHub (Mar 13, 2026).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/8569

Description

CUrrently, it seems that it is not possible to apply a created page model to an existing page in the same DB.
see the following video for demonstration : https://www.youtube.com/watch?v=BwcVOjSKIBo&t=24s

Impact

is not possible to apply a created page model to an existing page in the same DB.

Additional Context

No response

Originally created by @Ray0m on GitHub (Mar 13, 2026). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/8569 ### Description CUrrently, it seems that it is not possible to apply a created page model to an existing page in the same DB. see the following video for demonstration : https://www.youtube.com/watch?v=BwcVOjSKIBo&t=24s ### Impact is not possible to apply a created page model to an existing page in the same DB. ### Additional Context _No response_

mirror added the

new feature

database

labels

2026-03-23 21:34:06 +00:00

mirror commented

2026-03-23 21:34:07 +00:00

Author

Owner

@richardshiue commented on GitHub (Mar 16, 2026):

Hi @Ray0m, for starters, thank you so much for these bug reports, feature requests and improvements. They are very helpful and give us a ton of feedback on our product directions. I'm going through your reported issues and your video now.

As for this issue, yes. This is currently an unimplemented extension of the template feature. It would be a good idea to have it. I have renamed this issue to be more specific.

@richardshiue commented on GitHub (Mar 16, 2026): Hi @Ray0m, for starters, thank you so much for these bug reports, feature requests and improvements. They are very helpful and give us a ton of feedback on our product directions. I'm going through your reported issues and your video now. As for this issue, yes. This is currently an unimplemented extension of the template feature. It would be a good idea to have it. I have renamed this issue to be more specific. <img width="930" height="326" alt="Image" src="https://github.com/user-attachments/assets/4e7f300c-dad1-49ee-b036-85f3ec2b1a69" />

mirror commented

2026-03-23 21:34:07 +00:00

Author

Owner

@Ray0m commented on GitHub (Mar 16, 2026):

My pleasure @richardshiue, I have high hopes for Appflowy as a tool for my org so this is worth the effort atm.
I expect I will continue making reports in the same way (1 big vid cut up into smaller reports) with some regularity.
I have 3 questions for you :
Q1. Is there a roadmap of your dev timeline I could consult somewhere? It would help me plan ahead to know which function is to be expected when.
Q2. Would it be a problem if I would "spam" you guys with reports? :P like, I could post dozens of bugs and feature requests.... is it best to space them out or could I devote 1 day to reporting and publish a ton of them in one day? You tell me what would be best
Q3. Would it be possible to get a sense of level of urgency and dev timeline in response to the reports I make? I really don't need a specific day but knowing if my repported issues are to be expected in 2 weeks, 2 months or late this year would really help my planning.
thank you!

@Ray0m commented on GitHub (Mar 16, 2026): My pleasure @richardshiue, I have high hopes for Appflowy as a tool for my org so this is worth the effort atm. I expect I will continue making reports in the same way (1 big vid cut up into smaller reports) with some regularity. I have 3 questions for you : Q1. Is there a roadmap of your dev timeline I could consult somewhere? It would help me plan ahead to know which function is to be expected when. Q2. Would it be a problem if I would "spam" you guys with reports? :P like, I could post dozens of bugs and feature requests.... is it best to space them out or could I devote 1 day to reporting and publish a ton of them in one day? You tell me what would be best Q3. Would it be possible to get a sense of level of urgency and dev timeline in response to the reports I make? I really don't need a specific day but knowing if my repported issues are to be expected in 2 weeks, 2 months or late this year would really help my planning. thank you!

mirror commented

2026-03-23 21:34:08 +00:00

Author

Owner

@annieappflowy commented on GitHub (Mar 18, 2026):

Hi @Ray0m,

Please feel free to contact me on Discord. We greatly value your feedback! It is best to start each bug report or feature request as a GitHub issue, just like this one. If I have a follow-up question, I will reach out to you on Discord via DM.

When we complete or fix the issue, we'll close it here and you will receive a notification email from GitHub. For database-related bug reports, we aim to fix them as soon as they are received. For new feature requests, we currently prioritize those from paying customers.

Let me know if you have any further questions.

@annieappflowy commented on GitHub (Mar 18, 2026): Hi @Ray0m, Please feel free to contact me on Discord. We greatly value your feedback! It is best to start each bug report or feature request as a GitHub issue, just like this one. If I have a follow-up question, I will reach out to you on Discord via DM. When we complete or fix the issue, we'll close it here and you will receive a notification email from GitHub. For database-related bug reports, we aim to fix them as soon as they are received. For new feature requests, we currently prioritize those from paying customers. Let me know if you have any further questions.

mirror referenced this issue

2026-03-23 22:21:02 +00:00

[PR #3913] [MERGED] chore: share button text color in document #5947