add ability to generate work log #14716

New Issue

GiteaMirror · 2025-11-02T11:20:59-06:00

GiteaMirror commented

2025-11-02 11:20:59 -06:00

Originally created by @printfdebugging on GitHub (Jul 7, 2025).

Feature Description

i find the time tracking functionality on the issues really amazing, it's just awesome. it would be great if we have some way to generate a timelog on weekly and monthly basis at the user level, with various filters like label, project etc.

this way gitea would become one stop solution for working and time logging.

Screenshots

No response

Originally created by @printfdebugging on GitHub (Jul 7, 2025). ### Feature Description i find the time tracking functionality on the issues really amazing, it's just awesome. it would be great if we have some way to generate a timelog on weekly and monthly basis at the user level, with various filters like label, project etc. this way gitea would become one stop solution for working and time logging. ### Screenshots _No response_

GiteaMirror added the type/proposal label 2025-11-02 11:20:59 -06:00

GiteaMirror commented

2025-11-02 11:21:00 -06:00

@wxiaoguang commented on GitHub (Jul 7, 2025):

I think you meant this. You need to create an org first.

@wxiaoguang commented on GitHub (Jul 7, 2025): I think you meant this. You need to create an org first. ![Image](https://github.com/user-attachments/assets/9b2246b9-20cd-44ad-aa3b-3d90f23b5c4b)

GiteaMirror commented

2025-11-02 11:21:00 -06:00

@printfdebugging commented on GitHub (Jul 7, 2025):

yeah, i meant something like this but this misses the mark. first of all since time tracking is enabled at the repository level (as issues are local to a repository), it would make more sense to have something like this there. this is very abstract, hardly useful to determine anything.

i recently started using projects (repository local)

and i track everything in the issues, from my work logs (what i did, what i found...) to time logs (using the time tracker). having done that, i want some way to get a definitive report which i can share with my employers or look at myself and tell wehre's my time going.

having this Worktime tab at the user level would be the best in my opinion with some additional filtration criteria like "labels" and "project" so that i can label things appropriately as "work", "gitea-dev", "gtk" etc.. and by the end of the month see how much time i spent on each with a list of issues and total time spent on that issue. since time tracking happens at the issue level, it makes sense to list the issues.

if there are many issues, it might make more sense to organize issues into different projects instead of a single project, and then in that project the user can apply the label criteria.

oh, how about enabling it at the project level (for normal user accounts) and adding a button here

then each project has it's own time tracking with label filters and if someone has multiple projects to track, creating an organization would be better then. and we should add the "project" and "label" filter criteria in the above organization worktime tab as well.

@printfdebugging commented on GitHub (Jul 7, 2025): yeah, i meant something like this but this misses the mark. first of all since time tracking is enabled at the repository level (as issues are local to a repository), it would make more sense to have something like this there. this is very abstract, hardly useful to determine anything. i recently started using projects (repository local) ![Image](https://github.com/user-attachments/assets/cc49f149-0827-42f7-ab2d-2fc5d0bbe385) and i track everything in the issues, from my work logs (what i did, what i found...) to time logs (using the time tracker). having done that, i want some way to get a definitive report which i can share with my employers or look at myself and tell wehre's my time going. having this Worktime tab at the user level would be the best in my opinion with some additional filtration criteria like "labels" and "project" so that i can label things appropriately as "work", "gitea-dev", "gtk" etc.. and by the end of the month see how much time i spent on each with a list of issues and total time spent on that issue. since time tracking happens at the issue level, it makes sense to list the issues. if there are many issues, it might make more sense to organize issues into different projects instead of a single project, and then in that project the user can apply the label criteria. oh, how about enabling it at the project level (for normal user accounts) and adding a button here ![Image](https://github.com/user-attachments/assets/1d9d2a14-3c23-48cc-a4d0-12054fa604ab) then each project has it's own time tracking with label filters and if someone has multiple projects to track, creating an organization would be better then. and we should add the "project" and "label" filter criteria in the above organization worktime tab as well.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#14716