-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Add the ability to add estimated time to an issue #2615
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
So let's close this one since duplicated with #3003 |
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. |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as duplicate.
This comment was marked as duplicate.
i love gitea very much, i use gitea every day, |
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. |
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 |
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). |
Unfortunately an end or due date doesn't really let me log what I estimated for time vs what I logged in the issue. |
I encounter the same requirements. I'm trying to add this feature on gitea. I am on early stage, visible there: main...julienfastre:gitea:2615-add-estimated-time-to-issue (I am a newbie here, guidance and remarks are welcome!) |
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) |
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.
The text was updated successfully, but these errors were encountered: