mirror of
https://github.com/AppFlowy-IO/AppFlowy.git
synced 2026-03-24 04:46:56 +00:00
[GH-ISSUE #2811] [FR] Kanban - Allow re-ordering card properties #1214
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#1214
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 @jaggujajamensan on GitHub (Jun 15, 2023).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/2811
Originally assigned to: @Xazin on GitHub.
Description
I accidentally clicked the "hide" button on my kanban cards' due date, removing the property entirely from all my cards (don't really get the purpose of that button). Now when trying to re-add a date, it's inserted at the bottom, as such:

There's currently no way to put that date at the top again, unless I delete and re-add every other property.
Impact
This would punish users less for not having planned their entire card structure beforehand, and allow additions that don't go to the bottom.
Additional Context
Running latest release on Windows 10.
@annieappflowy commented on GitHub (Jun 15, 2023):
Thanks for your feedback! Will support re-ordering properties in Kanban.

There is a workaround at the moment. Go to Settings at the top right of your Kanban --> Click Layout ---> Grid
You can reorder properties in Grid and then switch back to Kanban
I tried to reproduce your issue with "Hide" but I am not quite sure about it.
Can you please elaborate on how you think Hide should work?
@jaggujajamensan commented on GitHub (Jun 15, 2023):
Thanks for the quick response, and for informing me about the grid workaround!
Glad to hear re-ordering card properties is a planned feature 😄
And the only issue with Hide was that I hadn't seen the visibility markers in the properties menu, sorry 😅
I was unsure of what the
Propertiesmenu represented at first, which is mostly my fault, but maybe other new users could be confused by that too.If other new users are confused by this as well, maybe the

Propertiesmenu would be slightly more intuitive if the "Properties" was renamed to "Card properties"? Or instead there could be a little title when opening that menu, like this:@annieappflowy commented on GitHub (Jun 15, 2023):
It's always the product designer's fault not our users!
For the hidden properties, we plan to introduce a visual clue (see the issue here)
In addition, I agree with you that we should make it more clear by adding more hints, eg: Database properties (2 shown).
Then in the property menu, add two headers for shown and hidden properties:
Shown in {the database name}
property 1
property 2
Hidden in {the database name}
property 3
@jaggujajamensan commented on GitHub (Jun 16, 2023):
Hints like that would be perfect! The feature is pretty intuitive once you understand it, so I think a few hints like that would be enough to make new users understand more easily
@Xazin commented on GitHub (Jul 12, 2023):
For now, I've made it possible to reorder properties from the settings menu by dragging.
Until we have the block action in the card menu, this should be sufficient.
See preview in #2989
@richardshiue commented on GitHub (Sep 26, 2023):
We now offer two ways of reordering card properties across 3 database view layouts: from the row detail page and from the settings menu. I consider this resolved