[GH-ISSUE #8483] [FR] Database Row/Card Templates - Auto-populate new rows with predefined structure #3877

New issue

Closed

opened 2026-03-23 21:33:49 +00:00 by mirror · 3 comments

mirror commented

2026-03-23 21:33:49 +00:00

Owner

Originally created by @eliko2000 on GitHub (Feb 14, 2026).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/8483

Description

I would like the ability to create templates for new rows/cards in databases (Grid/Board/Calendar views), similar to how Notion handles database templates.

Main use cases:

Bug tracking database - Each new bug report would automatically include predefined sections like in a specific area:

Description
Steps to reproduce
Expected behavior
Actual behavior
Root cause analysis

Project planning database - Each new project card should have a standard structure:

Project goals
Success metrics
Timeline
Stakeholders
Risk assessment

Meeting notes database - Each meeting entry should start with:

Agenda items
Discussion points
Action items
Decisions made

Impact

This feature would benefit:

Teams with standardized workflows - Ensures consistency across all entries
Individual users managing complex projects - Saves time by not recreating the same structure repeatedly
Knowledge workers - Maintains organized, structured information without manual effort

Current workaround:
Currently, I need to manually duplicate a "master" row each time, which is tedious and error-prone. Having a "Set as default template" option (similar to what was mentioned in Notion) would dramatically improve productivity.

Additional Context

This feature exists in Notion and is one of the main reasons users stick with it. For AppFlowy to be a true Notion alternative, especially for self-hosted users, this capability is essential. It would make AppFlowy significantly more powerful for real-world workflows where consistency and speed matter.
The template could be set at the database level, with an option to:

Set one default template for all new rows
Or have multiple templates to choose from when creating a new row (advanced feature)

Originally created by @eliko2000 on GitHub (Feb 14, 2026). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/8483 ### Description I would like the ability to create templates for new rows/cards in databases (Grid/Board/Calendar views), similar to how Notion handles database templates. Main use cases: Bug tracking database - Each new bug report would automatically include predefined sections like in a specific area: Description Steps to reproduce Expected behavior Actual behavior Root cause analysis Project planning database - Each new project card should have a standard structure: Project goals Success metrics Timeline Stakeholders Risk assessment Meeting notes database - Each meeting entry should start with: Agenda items Discussion points Action items Decisions made ### Impact This feature would benefit: Teams with standardized workflows - Ensures consistency across all entries Individual users managing complex projects - Saves time by not recreating the same structure repeatedly Knowledge workers - Maintains organized, structured information without manual effort Current workaround: Currently, I need to manually duplicate a "master" row each time, which is tedious and error-prone. Having a "Set as default template" option (similar to what was mentioned in Notion) would dramatically improve productivity. ### Additional Context This feature exists in Notion and is one of the main reasons users stick with it. For AppFlowy to be a true Notion alternative, especially for self-hosted users, this capability is essential. It would make AppFlowy significantly more powerful for real-world workflows where consistency and speed matter. The template could be set at the database level, with an option to: Set one default template for all new rows Or have multiple templates to choose from when creating a new row (advanced feature)

mirror closed this issue

2026-03-23 21:33:49 +00:00

mirror commented

2026-03-23 21:33:49 +00:00

Author

Owner

@richardshiue commented on GitHub (Feb 23, 2026):

Hi @eliko2000 Thank you so much for the detailed feature request! Can you check the latest release 0.11.2 and see if it fits your needs? Do let us know of any bugs that you encountered, improvements that we can make and whatever else that interferes with your workflow!

@richardshiue commented on GitHub (Feb 23, 2026): Hi @eliko2000 Thank you so much for the detailed feature request! Can you check the latest release 0.11.2 and see if it fits your needs? Do let us know of any bugs that you encountered, improvements that we can make and whatever else that interferes with your workflow!

mirror commented

2026-03-23 21:33:50 +00:00

Author

Owner

@eliko2000 commented on GitHub (Feb 23, 2026):

Hi @richardshiue ,
Thanks for answering. I updated my docker and app and I can't see where a template feature is available to try.

@eliko2000 commented on GitHub (Feb 23, 2026): Hi @richardshiue , Thanks for answering. I updated my docker and app and I can't see where a template feature is available to try.

mirror commented

2026-03-23 21:33:50 +00:00

Author

Owner

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

Supported in v0.11.3

@annieappflowy commented on GitHub (Mar 2, 2026): Supported in v0.11.3

mirror referenced this issue

2026-03-23 22:20:57 +00:00

[PR #3877] [MERGED] fix: calendar event editor field name overflow #5929