mirror of
https://github.com/AppFlowy-IO/AppFlowy.git
synced 2026-03-24 21:00:19 +00:00
[GH-ISSUE #3735] [FR] User lists which can be used across select and muti-select fields #10106
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#10106
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 @nfaux on GitHub (Oct 20, 2023).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/3735
Description
Having access to all lists (select, multi-select) across all document types. To reduce the need to repeat such things.
Impact
Significant time saver and reuse,
Additional Context
No response
@Xazin commented on GitHub (Oct 20, 2023):
One thing is having "access" to these fields, but how would you use them in documents? I'm really curious about your use-case here.
@nfaux commented on GitHub (Oct 20, 2023):
I have N projects and each project has a ToDo (Task) list. Being able to use the same list, e.g. the status list (option set), saves me having to create the same select list for each project.
Just an example. I may have easily overlooked some function/ability that is already present, but not easily found.
@richardshiue commented on GitHub (Oct 26, 2023):
Hi @nfaux, thanks for raising this suggestion. I think you may be referring to one of two things. Could you help me understand which fits your needs better?
@PeterHero commented on GitHub (Jan 2, 2024):
I second this request. Suggestion for users, one can create grid, name it as 'template-todo-grid' or so and then duplicate it when needed.