Automatically stop tracking time on one issue if I start tracking time on another

[bobemoe]

Currently if I'm already tracking time on an issue and view a different issue there is a notice saying that I am already tracking time and links to the issue I am tracking on. Good :)

It doesn't prevent me starting to track time on a second issue though. At this point the "already tracking time" message disappears (confusing) if I'm viewing one of the two issues I'm tracking time on.

If I view another issue, there is the "already tracking time" message but it only links to one of the two issue. (confusing - I never know I'm accidentally tracking two issues until I stop tracking on one and the notice remains). Personally I cant see a need to track time on two issues at once - is this a bug??

Maybe needs a config option if multiple tracking is deemed a required feature. Perhaps even 3 options Multiple Tracking: Prevent|Stop Other|Allow

[guillep2k]

I can see both use cases. I agree a setting to select one of the two forms would be required if the behavior is changed. There's however the question, does the time compute twice?

I'm labeling this also kind/bug because of the confusing UI feedback.

[bobemoe]

I split the only slightly related other idea into separate issue: #10539

[bobemoe]

As for your question, currently the time does compute twice, if I start tracking on two issues, and stop tracking 10 mins later on both issues, the I have clocked a total of 20 mins in a 10 min timespan! I can't really see a use case for that?

I'm not sure how else it could be handled without stopping (or pause/resume - complicated!?) the other issue?

[guillep2k]

@bobemoe Conceptually it's possible that two issues are so related that when you work in a PR to fix one you're also working to fixing the other. IMHO, however, handling such a complex schedule is out of the scope of Gitea. So I'd say we should pause the old issue when a new issue is started working on. I'd show a warning dialog before submitting, though.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.