-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Removing of spent time in Issue activity results in 404 if time tracking is disabled #29233
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
Comments
lunny
pushed a commit
that referenced
this issue
Feb 20, 2024
Fix #29233 The delete button of time logs won't be shown when the time tracker is disabled. 
Zettat123
added a commit
to Zettat123/gitea
that referenced
this issue
Feb 20, 2024
Fix go-gitea#29233 The delete button of time logs won't be shown when the time tracker is disabled. 
KN4CK3R
added a commit
that referenced
this issue
Feb 20, 2024
) Backport #29257 Fix #29233 The delete button of time logs won't be shown when the time tracker is disabled.  Co-authored-by: KN4CK3R <[email protected]>
silverwind
pushed a commit
to silverwind/gitea
that referenced
this issue
Feb 20, 2024
Fix go-gitea#29233 The delete button of time logs won't be shown when the time tracker is disabled. 
project-mirrors-bot-tu bot
pushed a commit
to project-mirrors/forgejo-as-gitea-fork
that referenced
this issue
Jan 23, 2025
…) (go-gitea#29279) Backport go-gitea#29257 Fix go-gitea#29233 The delete button of time logs won't be shown when the time tracker is disabled.  Co-authored-by: KN4CK3R <[email protected]> (cherry picked from commit e940443)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
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
The text was updated successfully, but these errors were encountered: