Closed
Description
Description
If time was tracked and then time tracking is disabled (in my case at repo scope) the frontend still allows for deletion of the time log. this results in a 404. if time tracking is enabled again, this endpoint now works.
Url of endpoint: https://gitea.local/ORG/repo/issues/1/times/1/delete
Maybe remove time tracking
- deletion
- in general
from the frontend if disabled.
I wasn't able to use https://try.gitea.io/ for reproduction, as it's login seems to be down
Gitea Version
1.21.5
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
Git Version
No response
Operating System
Windows Server
How are you running Gitea?
Standalone windows
Database
MSSQL