mirror of
https://github.com/AppFlowy-IO/AppFlowy.git
synced 2026-03-24 21:00:19 +00:00
[GH-ISSUE #3942] [FR] Separate TextField for creating new Option in Databases. #1785
Labels
No labels
2024
2025
2026
acct mgmt
AI
automation
bug
calendar
ci
CJK
cloud
code-block
collaboration
copy-paste
database
data migration
data sync
deploy
desktop
develop
develop
documentation
duplicate
editor
editor-plugin
emoji
export
files
flutter-only
follow-up
formula
good first issue for devs
good first issue for experienced devs
grid
hacktoberfest
HACKTOBERFEST-ACCEPTED
help wanted
i18n
icons
images
importer
improvements
infra
install
integrations
IR
kanban board
login
look and joy
mentorship
mobile
mobile
needs design
new feature
new feature
non-coding
notes
notifications
onboarding
organization
P0+
permission
platform-linux
platform-mac
platform-windows
plugins
program
pull-request
Q1 25
Q1 26
Q2 24
Q2 25
Q3 24
Q3 25
Q4 24
Q4 25
react
regression
rust
rust
Rust-only
Rust-only
Rust-starter
Rust-starter
self-hosted
shortcuts
side panel
slash-menu
sync v2
table
tablet
task
tauri
templates
tests
themes
translation
v0.5.6
v0.5.8
v0.5.9
v0.6.0
v0.6.1
v0.6.4
v0.6.7
v0.6.8
v0.7.1
v0.7.4
v0.7.4
v0.7.5
v0.7.6
v0.7.7
v0.7.8
v0.8.0
v0.8.4
v0.8.5
v0.8.9
web
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
AppFlowy-IO/AppFlowy#1785
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @MayurSMahajan on GitHub (Nov 15, 2023).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/3942
Description
In the current version of AppFlowy, when you want to create a new option in multi-select or select attribute in Databases. There is a single textfield which appears at the top, this TextField can be used to:
It has been noted that this is a bit confusing for Users. And they would like two separate fields each for its special purpose.
The existing UI:

Impact
All Users
Additional Context
I find it confusing from the user's point of view if he has to proceed differently to add options in the column of a table.
Option 1 (input via the header): You click in the header of a table and select "Edit property". If you then click on the "Add option" button, an additional text input field appears at the top of the list and you can then add a new option there (see screenshots).
Option 2 (input in the cell of a row): If you click in a cell in the table, "Select an option or create one" and a plus-button appear. Now the user presses the plus-button (see screenshot), but the user wonders why an additional text field does not appear again as with option 1. How is he supposed to know that in this case he should enter the name of a new option in the search field? In this case too, an additional text field should appear at the top of the list, as with option 1. Otherwise it would be a break in the concept.
-- Mac Meikel, originally posted in Discord
@annieappflowy commented on GitHub (Apr 1, 2024):
This feature has been improved per the user feedback
