Date for time tracking #5429

New Issue

GiteaMirror · 2025-11-02T06:24:40-06:00

GiteaMirror commented

2025-11-02 06:24:40 -06:00

Originally created by @ddrv on GitHub (May 19, 2020).

Please, add date field into time tracking form (on issue page)

Originally created by @ddrv on GitHub (May 19, 2020). Please, add `date` field into time tracking form (on issue page)

GiteaMirror added the outdated/theme/timetracker issue/confirmed type/proposal labels 2025-11-02 06:24:40 -06:00

GiteaMirror commented

2025-11-02 06:24:41 -06:00

@stale[bot] commented on GitHub (Jul 18, 2020):

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.

@stale[bot] commented on GitHub (Jul 18, 2020): 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.

GiteaMirror commented

2025-11-02 06:24:41 -06:00

@mlthlschr commented on GitHub (Nov 29, 2020):

Right now, the model only accepts created as date, linking the spent time to that very date. It would either require the possibility of manipulating the created Date, or an additional property representing the actual starting date. In any case, it would require an additional (optional) parameter in POST /repos/{owner}/{repo}/issues/{index}/times.

@mlthlschr commented on GitHub (Nov 29, 2020): Right now, the model only accepts `created` as date, linking the spent time to that very date. It would either require the possibility of manipulating the `created` Date, or an additional property representing the actual starting date. In any case, it would require an additional (optional) parameter in `POST /repos/{owner}/{repo}/issues/{index}/times`.

GiteaMirror commented

2025-11-02 06:24:41 -06:00

@ftrueck commented on GitHub (Mar 15, 2025):

I think the created field would work fine for it, except if you wish to track when the time was originally added, but then you would need an additional date field which makes things even more complex. I do not understand why this never was considered to be added though. It would make the time tracking finally (more) usable.

@ftrueck commented on GitHub (Mar 15, 2025): I think the created field would work fine for it, except if you wish to track when the time was originally added, but then you would need an additional date field which makes things even more complex. I do not understand why this never was considered to be added though. It would make the time tracking finally (more) usable.

GiteaMirror referenced this issue

2025-11-02 15:49:48 -06:00

[PR #5429] [MERGED] fix forgot removed records when deleting user #17793

GiteaMirror referenced this issue

2025-11-02 16:00:39 -06:00

[PR #5509] [MERGED] fix undeleted content when deleting user #17819

GiteaMirror referenced this issue

2025-11-02 16:12:22 -06:00

[PR #5562] [MERGED] fix table name typo on SQL #17843

Sign in to join this conversation.