You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 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.
Feature Description
As the PR is merged, there's no need to use time tracker.
Screenshots
No response
The text was updated successfully, but these errors were encountered: