Feature request: Time tracking #362

Closed
opened 2025-11-02 03:20:11 -06:00 by GiteaMirror · 17 comments
Owner

Originally created by @mixedCase on GitHub (Feb 18, 2017).

Gogs issue describing the idea behind the request: https://github.com/gogits/gogs/issues/879

GitLab implements it for its Enterprise version. It would be a killer feature for Gitea to have this.


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Originally created by @mixedCase on GitHub (Feb 18, 2017). Gogs issue describing the idea behind the request: https://github.com/gogits/gogs/issues/879 GitLab implements it for its Enterprise version. It would be a killer feature for Gitea to have this. <bountysource-plugin> --- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/42166141-feature-request-time-tracking?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github). </bountysource-plugin>
GiteaMirror added the outdated/theme/timetrackertype/feature labels 2025-11-02 03:20:11 -06:00
Author
Owner

@lunny commented on GitHub (Feb 18, 2017):

I'm not very clear with this feature.

@lunny commented on GitHub (Feb 18, 2017): I'm not very clear with this feature.
Author
Owner

@mixedCase commented on GitHub (Feb 18, 2017):

@lunny Example for GitLab: https://docs.gitlab.com/ee/workflow/time_tracking.html

@mixedCase commented on GitHub (Feb 18, 2017): @lunny Example for GitLab: https://docs.gitlab.com/ee/workflow/time_tracking.html
Author
Owner

@kolaente commented on GitHub (Jul 19, 2017):

Or we could simply make a button next to the issue "Start Timetracking" and once you're finished you would just click "Stop Timetracking" and it would save the time spent with the issue. Like you can do it in Flyspray.

With this, you wouldnt need an extra tool for timetracking.

@kolaente commented on GitHub (Jul 19, 2017): Or we could simply make a button next to the issue "Start Timetracking" and once you're finished you would just click "Stop Timetracking" and it would save the time spent with the issue. Like you can do it in Flyspray. With this, you wouldnt need an extra tool for timetracking.
Author
Owner

@jonasfranz commented on GitHub (Jul 24, 2017):

My Concept:

  1. "Start" button for timetracking starts a sort of stopwatch.
  2. "Stop" button stops the stopwatch and creates a record with the timedifference between the startdate and the stopdate.
  3. The tracked time appeares as a reference in the issue (like commit references)
  4. At the right sidebar appears a listing of the tracked time in total per user.
@jonasfranz commented on GitHub (Jul 24, 2017): My Concept: 1. "Start" button for timetracking starts a sort of stopwatch. 2. "Stop" button stops the stopwatch and creates a record with the timedifference between the startdate and the stopdate. 3. The tracked time appeares as a reference in the issue (like commit references) 4. At the right sidebar appears a listing of the tracked time in total per user.
Author
Owner

@lunny commented on GitHub (Jul 24, 2017):

A Start button near the Close button. After click Start button and started, Start button will be changed to Finished button. Click Finished button or a commit with close tag both are ok. Simple click Close button will mean give up the issue.

@lunny commented on GitHub (Jul 24, 2017): A `Start` button near the `Close` button. After click `Start` button and started, `Start` button will be changed to `Finished` button. Click `Finished` button or a commit with close tag both are ok. Simple click `Close` button will mean give up the issue.
Author
Owner

@kolaente commented on GitHub (Jul 24, 2017):

I like the idea, but i would propose to move the button also to the right, where the other options are.

@kolaente commented on GitHub (Jul 24, 2017): I like the idea, but i would propose to move the button also to the right, where the other options are.
Author
Owner

@lunny commented on GitHub (Jul 24, 2017):

I like the button near the Close so reminder the user to click the finish but not close.

@lunny commented on GitHub (Jul 24, 2017): I like the button near the `Close` so reminder the user to click the `finish` but not `close`.
Author
Owner

@jonasfranz commented on GitHub (Jul 24, 2017):

There is a bounty posted on this issue.
Bountysource

@jonasfranz commented on GitHub (Jul 24, 2017): There is a bounty posted on this issue. [![Bountysource](https://api.bountysource.com/badge/issue?issue_id=42166141)](https://www.bountysource.com/issues/42166141-feature-request-time-tracking?utm_source=42166141&utm_medium=shield&utm_campaign=ISSUE_BADGE)
Author
Owner

@jonasfranz commented on GitHub (Jul 24, 2017):

@lunny I agree with @kolaente because a button at the right sidebar would be more convenient because of the existence of the "Subscribe" button. It could be placed below this button in an equal style with other icons.

Having the button near the close button could point out that the user must write a comment to track his/her time but you rarely write a comment and track the spent time simultaneously.

@jonasfranz commented on GitHub (Jul 24, 2017): @lunny I agree with @kolaente because a button at the right sidebar would be more convenient because of the existence of the "Subscribe" button. It could be placed below this button in an equal style with other icons. Having the button near the close button could point out that the user must write a comment to track his/her time but you rarely write a comment and track the spent time simultaneously.
Author
Owner

@jonasfranz commented on GitHub (Jul 24, 2017):

I've made a smll UI draft. What do you think?
An alternative according to @lunny will be theire soon.
Time Tracker Finish
Time Tracker Start

@jonasfranz commented on GitHub (Jul 24, 2017): I've made a smll UI draft. What do you think? An alternative according to @lunny will be theire soon. ![Time Tracker Finish](https://cloud.jonasfranz.software/index.php/apps/files_sharing/ajax/publicpreview.php?x=1920&y=579&a=true&file=time_tracker_finish.png&t=k5lULSSZZNi0zvJ&scalingup=0 "Time Tracker Finish") ![Time Tracker Start](https://cloud.jonasfranz.software/index.php/apps/files_sharing/ajax/publicpreview.php?x=1920&y=579&a=true&file=time_tracker_start.png&t=b2u55RXvBKVGbcR&scalingup=0 "Time Tracker Start")
Author
Owner

@kolaente commented on GitHub (Jul 24, 2017):

Colors would be nice, maybe yellow to indicate it's currently tracking.

@kolaente commented on GitHub (Jul 24, 2017): Colors would be nice, maybe yellow to indicate it's currently tracking.
Author
Owner

@lafriks commented on GitHub (Jul 24, 2017):

Also option to enable/disable time tracking for organization/repository/server would be great

@lafriks commented on GitHub (Jul 24, 2017): Also option to enable/disable time tracking for organization/repository/server would be great
Author
Owner

@jonasfranz commented on GitHub (Jul 24, 2017):

timetracking_new

  • The "+" button let the user add spent time manually by a modal.
  • The "Start" button will start a stopwatch
  • Every time tracking event will be logged in the timeline
  • Under the Start / + button is a list of the total time spent by the users
@jonasfranz commented on GitHub (Jul 24, 2017): ![timetracking_new](https://user-images.githubusercontent.com/5757182/28544803-d3a41d7e-70c4-11e7-8a98-573db09ec529.png) * The "+" button let the user add spent time manually by a modal. * The "Start" button will start a stopwatch * Every time tracking event will be logged in the timeline * Under the Start / + button is a list of the total time spent by the users
Author
Owner

@lafriks commented on GitHub (Jul 24, 2017):

I think button "Add" will be much clearer than "+"

@lafriks commented on GitHub (Jul 24, 2017): I think button "Add" will be much clearer than "+"
Author
Owner

@Caballerog commented on GitHub (Oct 1, 2017):

I'm testing this feature, which I think that is very useful, but should allow the user modify or delete a time tracking event because It can make a mistake. Good job!! :-)

@Caballerog commented on GitHub (Oct 1, 2017): I'm testing this feature, which I think that is very useful, but should allow the user modify or delete a time tracking event because It can make a mistake. Good job!! :-)
Author
Owner

@daviian commented on GitHub (Oct 1, 2017):

@Caballerog Please create a new issue for this feature request.

@daviian commented on GitHub (Oct 1, 2017): @Caballerog Please create a new issue for this feature request.
Author
Owner

@Caballerog commented on GitHub (Oct 3, 2017):

@daviian Thanks ;-) rel https://github.com/go-gitea/gitea/issues/2642

@Caballerog commented on GitHub (Oct 3, 2017): @daviian Thanks ;-) rel https://github.com/go-gitea/gitea/issues/2642
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#362