Add the ability to add estimated time to an issue #1100

Closed
opened 2025-11-02 03:48:40 -06:00 by GiteaMirror · 16 comments
Owner

Originally created by @kolaente on GitHub (Sep 27, 2017).

Originally assigned to: @lafriks on GitHub.

It would be cool if you could add estimated time to an issue to better plan the workflow.

@JonasFranzDEV this is probably relevant for you.

Originally created by @kolaente on GitHub (Sep 27, 2017). Originally assigned to: @lafriks on GitHub. It would be cool if you could add estimated time to an issue to better plan the workflow. @JonasFranzDEV this is probably relevant for you.
GiteaMirror added the type/featureissue/confirmed labels 2025-11-02 03:48:40 -06:00
Author
Owner

@lunny commented on GitHub (Nov 29, 2017):

So let's close this one since duplicated with #3003

@lunny commented on GitHub (Nov 29, 2017): So let's close this one since duplicated with #3003
Author
Owner

@gsantner commented on GitHub (Apr 18, 2019):

@lunny
I think this can be reopened as #3003 didn't handle estimated time. At least as in current commit 3fb038c theres no way to set time estimation.

@gsantner commented on GitHub (Apr 18, 2019): @lunny I think this can be reopened as #3003 didn't handle `estimated time`. At least as in current commit 3fb038c theres no way to set time estimation.
Author
Owner

@stale[bot] commented on GitHub (Jun 22, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Jun 22, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
Author
Owner

@jsanchezba commented on GitHub (May 19, 2020):

Would be cool to show the total amount on a milestone

Something like:

image

@jsanchezba commented on GitHub (May 19, 2020): Would be cool to show the total amount on a milestone Something like: ![image](https://user-images.githubusercontent.com/13497454/98419273-00238880-2085-11eb-8989-47d160f64a86.png)
Author
Owner

@Eistime commented on GitHub (Aug 31, 2020):

this feature could make my life 100 times easier! hope you guys doing well! animo! :)

@Eistime commented on GitHub (Aug 31, 2020): this feature could make my life 100 times easier! hope you guys doing well! animo! :)
Author
Owner

@MrHaroldA commented on GitHub (Mar 23, 2022):

Any progress on this?

@MrHaroldA commented on GitHub (Mar 23, 2022): Any progress on this?
Author
Owner

@ivancxj commented on GitHub (Apr 9, 2022):

have plan?

@ivancxj commented on GitHub (Apr 9, 2022): have plan?
Author
Owner

@ZJM6658 commented on GitHub (Apr 15, 2022):

i love gitea very much, i use gitea every day,
this feature could goes well with my work !
i hope you guys have a plan ~

@ZJM6658 commented on GitHub (Apr 15, 2022): i love gitea very much, i use gitea every day, this feature could goes well with my work ! i hope you guys have a plan ~
Author
Owner

@chriswnz commented on GitHub (Sep 4, 2022):

Would use this feature, without firing up a project management system, it's a quick way to check how time spent is going.

Love Gitea thanks to everyone involved.

@chriswnz commented on GitHub (Sep 4, 2022): Would use this feature, without firing up a project management system, it's a quick way to check how time spent is going. Love Gitea thanks to everyone involved.
Author
Owner

@delvh commented on GitHub (Sep 4, 2022):

Hasn't this already been implemented already for a long time?
image

@delvh commented on GitHub (Sep 4, 2022): Hasn't this already been implemented already for a long time? ![image](https://user-images.githubusercontent.com/51889757/188305718-bdd3cb36-8839-453f-9e7c-02bdd28e836f.png)
Author
Owner

@lafriks commented on GitHub (Sep 4, 2022):

That's spent time - estimated time is for planning to set estimated time on how much time would be needed to fix/implement issue

@lafriks commented on GitHub (Sep 4, 2022): That's spent time - estimated time is for planning to set estimated time on how much time would be needed to fix/implement issue
Author
Owner

@lunny commented on GitHub (Sep 4, 2022):

That's spent time - estimated time is for planning to set estimated time on how much time would be needed to fix/implement issue

We already have start date, maybe an end date could satisfy the requirement and that will be a base of gantte graph

@lunny commented on GitHub (Sep 4, 2022): > That's spent time - estimated time is for planning to set estimated time on how much time would be needed to fix/implement issue We already have start date, maybe an end date could satisfy the requirement and that will be a base of gantte graph
Author
Owner

@GeNTooFReaK commented on GitHub (Sep 4, 2022):

We already have start date, maybe an end date could satisfy the requirement and that will be a base of gantte graph

In this issue (feature request) it's wanted to set estimated time in the manner of "implementing this is estimated to take 8 hours" and later be able to compare it to the actual time spent. GitLab has this feature (estimated and spent time).

@GeNTooFReaK commented on GitHub (Sep 4, 2022): > We already have start date, maybe an end date could satisfy the requirement and that will be a base of gantte graph In this issue (feature request) it's wanted to set estimated time in the manner of "implementing this is estimated to take 8 hours" and later be able to compare it to the actual time spent. GitLab has this feature (estimated and spent time).
Author
Owner

@chriswnz commented on GitHub (Sep 4, 2022):

Unfortunately an end or due date doesn't really let me log what I estimated for time vs what I logged in the issue.
Even if I had the luxury of only working on a single issue at a time to make that work, the granularity on due date is entire days where an issue may only be estimated at 3 hours.
It would also help with selecting issues to work on by selecting issues that might have a lower priority but can be cleared in a short amount of time. Sometimes its nice just to clear a few.
Thanks.

@chriswnz commented on GitHub (Sep 4, 2022): Unfortunately an end or due date doesn't really let me log what I estimated for time vs what I logged in the issue. Even if I had the luxury of only working on a single issue at a time to make that work, the granularity on due date is entire days where an issue may only be estimated at 3 hours. It would also help with selecting issues to work on by selecting issues that might have a lower priority but can be cleared in a short amount of time. Sometimes its nice just to clear a few. Thanks.
Author
Owner

@julienfastre commented on GitHub (Nov 7, 2022):

I encounter the same requirements. I'm trying to add this feature on gitea. I am on early stage, visible there: https://github.com/go-gitea/gitea/compare/main...julienfastre:gitea:2615-add-estimated-time-to-issue (I am a newbie here, guidance and remarks are welcome!)

@julienfastre commented on GitHub (Nov 7, 2022): I encounter the same requirements. I'm trying to add this feature on gitea. I am on early stage, visible there: https://github.com/go-gitea/gitea/compare/main...julienfastre:gitea:2615-add-estimated-time-to-issue (I am a newbie here, guidance and remarks are welcome!)
Author
Owner

@denyskon commented on GitHub (Jul 1, 2023):

This seems to be discussed actively/worked on in #23112. I think it is better to close this to prevent issue duplication (even though this issue is way older)

@denyskon commented on GitHub (Jul 1, 2023): This seems to be discussed actively/worked on in #23112. I think it is better to close this to prevent issue duplication (even though this issue is way older)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#1100