search

go-gitea / gitea

Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD
https://gitea.com
MIT License
42.98k stars 5.31k forks source link

Merged PR should hidden time tracker? #30989

Open yp05327 opened 1 month ago

yp05327 commented 1 month ago

Feature Description

image

As the PR is merged, there's no need to use time tracker.

Screenshots

No response

kemzeb commented 1 month ago

I would also argue that we shouldn't be able to set a due date on a merged PR since to my knowledge users would only use this feature to ensure that they code review/merge PRs in a timely manner. Not sure if it's used beyond that

silverwind commented 1 month ago

I would also argue that we shouldn't be able to set a due date on a merged PR since to my knowledge users would only use this feature to ensure that they code review/merge PRs in a timely manner. Not sure if it's used beyond that

I think you are talking about a different topic, but I agree, due date on closed PR/issue makes no sense and we should hide that section.

On topic of time tracker: Not sure, maybe some users prefer to retroactively book time into a PR, thought I guess we should not encourage such practives. In fact I think we should automatically stop any active timers when a PR is merged. Maybe keep this behaviour configurable, thought.