-
-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Broke AppFlowy Boards by changing Status to Date #6816
Comments
Hi @Oshirowanen, thanks for raising this issue. I'm trying to understand the issue you're facing better. When you change the type of the property currently being used to group the cards, the board will try to find another one. Here's a new board that I followed the steps you laid out, maybe there was a step or two that I missed somewhere along the way? Screen.Recording.2024-11-25.at.8.00.02.PM.movWhen you say that you can no longer get into the board, do you mean that it shows an error or an infinite loading icon? If you could record of a video of this happening, it would help me a ton in trying to find the cause. |
Sorry about the badly worded post, it was done in a rush. I have now updated the post and have included a video to show the steps more clearly. I hope the updated post clarifies the issue. I can confirm that I get the same issue on Windows 11 and Ubuntu 24.04. |
Hi @Oshirowanen, thanks for the update. Yes I can reproduce it now, I will see to fixing this issue as soon as possible. |
Bug Description
I somehow was able to chose "date" in a board, and now I can no longer get into the board.
How to Reproduce
Open any board
click Settings > Properties > Status
Select Date
Click out of the board and then try to get back in.
Expected Behaviour
If this is going to break the board, I shouldn't be able to make such a change.
I should at least be able to check the status back to a default value to bring the board contents back.
Operating System
Ubuntu 24.04
Windows 11
AppFlowy Version(s)
0.7.3
Video recording
2024-11-25.14-32-30.mp4
Screenshots
No response
Additional Context
The text was updated successfully, but these errors were encountered: