Skip to content
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

Add time tracking features for project management #3003

Closed
yomeuh opened this issue Nov 27, 2017 · 6 comments · Fixed by #3341
Closed

Add time tracking features for project management #3003

yomeuh opened this issue Nov 27, 2017 · 6 comments · Fixed by #3341
Labels
type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first.
Milestone

Comments

@yomeuh
Copy link

yomeuh commented Nov 27, 2017

Description

Maybe others would like such enhancements, our team would love them to evaluate our project plans

  • ability to see time tracking value in issues list
  • ability to see the total time tracking at the end of the list, at least in the issues list for a specific milestone
  • as an extra, ability to set "time planned" to compare with effective time
    snapshot-issue-list
    snapshot-time-planned
    snapshot-total-time
    snapshot-milestone-stats
@lunny lunny added the type/proposal The new feature has not been accepted yet but needs to be discussed first. label Nov 27, 2017
@kolaente
Copy link
Member

This overlaps with #2615 I think, but yours goes deeper.

@lunny lunny added the type/feature Completely new functionality. Can only be merged if feature freeze is not active. label Nov 29, 2017
@lunny lunny added this to the 1.x.x milestone Nov 29, 2017
@xak2000
Copy link

xak2000 commented Feb 2, 2018

Also it should be possible to edit or at least remove already tracked time.

For example:

  • I can accidentally track wrong number (80h instead of 8h).
  • I can forget to press "stop" button after "start" and remember this after two weeks.

And it should be possible to undo this or change these tracked values, or else it would be to dangerous function to use.

@kolaente
Copy link
Member

kolaente commented Feb 2, 2018

@xak2000 would you mind opening a separate issue for this?

@xak2000
Copy link

xak2000 commented Feb 2, 2018

Is this issue alreay implemented? I thought it can be part of this issue (see bullets in first message).
Opened #3447.

@lunny lunny modified the milestones: 1.x.x, 1.5.0 Apr 29, 2018
@MrHaroldA
Copy link

MrHaroldA commented Aug 13, 2018

It looks like #3341 fixes all, but:

as an extra, ability to set "time planned" to compare with effective time

I can't seem to find a separate request for that? Is this still on the project scope? This will allow us to plan our milestones/sprints without the need of a calculator ;)

@lunny
Copy link
Member

lunny commented Aug 13, 2018

There are no plan time in current implementation I think.

@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants