I suggest you ...

Add time tracking for issues similar to Feng office

It would be great if gitlab would save information on how much time given task or issue took, so that we can create reports on the project, per user, per milestone and so forth

377 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Tomáš Plešek shared this idea  ·   ·  Admin →

    55 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Muhammad Fuzail Zubari commented  · 

        @GitLab team Can you please tell me when core team of GitLab is going to add a feature of time estimate of each issue?

      • Nerv _ commented  · 

        +1 for this feature

        @Stephen =)

      • Eugene commented  · 

        @Stephen Thx! I will try your suggestion

      • Eugene commented  · 

        HI! Please tell me, is there a way to take the time tracking to interface gitlab?
        Maybe someone knows a plugin for this?

      • Stephen commented  · 

        Milestone Budget support has been added.
        the CSV now downloads as a xlsx with two worksheets: Issues and Milestones.

        Anyone have interest in Issues Budgets?

      • Stephen commented  · 

        Bootstrap has been added as well as Auto-pagination of Issues and Comments. Next support will be for logging into different endpoints other than GitLab.com.
        I am looking for support from people to help build out the GitLab OmniAuth gem. gem could use a little love, + the GitLab Ruby API wrapper could use better oAuth2 support. I am no expert in that area, so if anyone is familar with this, support in building out the oauth2 support would be greatly appreciated.

        I will also be providing some Excel Pivot table template reports that you can copy your CSV data into. This should help with seeing what is possible in the current structure. Obviously longer term we can add support for interactive reports and charting directly in the app.

      • Stephen commented  · 

        Okay the first iteration of the MVP is up in the repo: https://github.com/StephenOTT/GitLab-Time-Tracking.

        See the readme for more details.

        Basic functionality:
        1. Download Time Tracking Data from Repo/Project into MongoDB
        2. Download CSV version of Time Tracking Data.

        Largest missing feature at the moment for this iteration is the lack of API auto-pagination. If the Project has more than 100 issues or more than 100 comments in a issue, there will be missing data. Should should be resolved shortly.

      • Stephen commented  · 

        Okay, I have finally got around to getting this going. Sorry for the long delay. Many different projects going on.

        See this repo to track progress and log any requests or issues: https://github.com/StephenOTT/GitLab-Time-Tracking

        I am going towards a lightweight Sinatra application as the MVP for flexibility and simplicity. It will log you in through OAuth2. At the moment it downloads all Issues and Comments and then does a analysis of the comments and looks for the Time Tracking information. There are several improvements we can make around this process, but simplicity is key at the moment. Data is downloaded into MongoDB we can use the Aggregation Framework (or map reduce if you want to get fancy) to provide the breakdowns similar to the GitHub-Time-Tracking application.

        I am looking for people to suggest what "views" of information are most valuable. Please provide these in the issue queue.

      • Anonymous commented  · 

        Just wanted to ask about the progress. Really looking forward for time/estimate tracking.

      • Stephen commented  · 

        The more i review this, I think it makes more sense to build this as a secondary app that pulls the data for reporting purposes.

        Building it into the core GL has major design issues when we want to extend for more tracking.

        I Have more time lately. I will pull up my previous GitHub-Time-Tracking Code and integrate GL API into it. We could even use GL's background processor sidekiq to schedule the scrapes.

      • Kevin Kirsche commented  · 

        I would be extremely interested in this. I may be interested in doing a pull request for this with more information about the "Few Adjustments"

      • Alys commented  · 

        My organisation has recently adopted GitLab and we'd like to be able to record a time estimate for an issue and see the sum of these for all issues in a milestone. This would make the milestone view perfect for sprint planning and would allow an accurate progress bar.

        I also use Trello and the "Scrum for Trello" plugindoes this without changes to the core data model. Time estimates and/or elapsed time can be entered using special syntax and are formatted and displayed on the Trello cards with totals shown at the top of each list.

        I would vote for making at least the basic recording and display of time estimates and/or logged time a core feature. There is lots of scope to build on it for more advanced reporting, burndown charts etc which could be implimented in separate apps perhaps.

      • Alexander commented  · 

        Any news?
        I think a lot of developers are waiting the time tracking feature!

      • Stephen commented  · 

        Hey
        So what are you needs? Even if the time was added how would you report on it?

        This is why I was think a secondary app would be best. Something that provides the reporting and logic. Thoughts?

      • Jaroslav commented  · 

        Any update on this request? It's the only thing stopping us from fully moving to gitlab from redmine

      ← Previous 1 3

      Feedback and Knowledge Base