[Bug]: Project gets automatically locked even when left unlocked by the user #871

Open
opened 2026-02-04 21:31:43 +03:00 by OVERLORD · 3 comments
Owner

Originally created by @PrabhatDagar on GitHub (Nov 27, 2025).

Where is the problem occurring?

I encountered the problem while using the application (Frontend)

What browsers are you seeing the problem on?

Microsoft Edge

Current behavior

When a user leaves a project in an unlocked state and navigates back to the home page, the project unexpectedly becomes locked. When the user clicks on the project again from the home page, it appears as locked, even though the user did not manually lock it before leaving.

This behaviour can confuse users and interrupts the normal workflow, as the project state is not being preserved correctly.

Before

Image

After

Image

Desired behavior

The project should remain in the same state as the user left it.
If the user leaves the project unlocked, it should still be unlocked when they return from the home page.

Steps to reproduce

-Go to the project

  • Unlock the project
  • Go back to Home
  • Click on the project again
  • Notice the behaviour

Other information

No response

Originally created by @PrabhatDagar on GitHub (Nov 27, 2025). ### Where is the problem occurring? I encountered the problem while using the application (Frontend) ### What browsers are you seeing the problem on? Microsoft Edge ### Current behavior When a user leaves a project in an unlocked state and navigates back to the home page, the project unexpectedly becomes locked. When the user clicks on the project again from the home page, it appears as locked, even though the user did not manually lock it before leaving. This behaviour can confuse users and interrupts the normal workflow, as the project state is not being preserved correctly. Before <img width="3177" height="1806" alt="Image" src="https://github.com/user-attachments/assets/589372f0-ff1c-4b56-a871-06da410a4265" /> After <img width="3192" height="1746" alt="Image" src="https://github.com/user-attachments/assets/d17c0ed9-283d-41d8-8374-70ef0771ddba" /> ### Desired behavior The project should remain in the same state as the user left it. If the user leaves the project unlocked, it should still be unlocked when they return from the home page. ### Steps to reproduce -Go to the project - Unlock the project - Go back to Home - Click on the project again - Notice the behaviour ### Other information _No response_
Author
Owner

@PrabhatDagar commented on GitHub (Nov 27, 2025):

@meltyshev Hi, do you think this could be marked as a “good first issue” as it seems beginner-friendly and well-scoped?

@PrabhatDagar commented on GitHub (Nov 27, 2025): @meltyshev Hi, do you think this could be marked as a “good first issue” as it seems beginner-friendly and well-scoped?
Author
Owner

@meltyshev commented on GitHub (Nov 27, 2025):

Hey! We actually did it that way on purpose, but I totally get that it can be annoying - especially if you're trying to edit things across multiple projects. I'll first check if it's okay to make it always keep the state, or maybe we could add a user setting for that...

@meltyshev commented on GitHub (Nov 27, 2025): Hey! We actually did it that way on purpose, but I totally get that it can be annoying - especially if you're trying to edit things across multiple projects. I'll first check if it's okay to make it always keep the state, or maybe we could add a user setting for that...
Author
Owner

@dahamsta commented on GitHub (Jan 20, 2026):

Is it possible to disable locking, temporarily or permanantly? My Planka install is single user, it's really not needed.

@dahamsta commented on GitHub (Jan 20, 2026): Is it possible to disable locking, temporarily or permanantly? My Planka install is single user, it's really not needed.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/planka#871