Time tracking in the future

There are a lot of things we want to achieve with Time Tracking. Here is a list of what could come in future releases.

This list is for information purposes only. Things can change anytime.

• Reports: https://gitlab.com/gitlab-org/gitlab-ee/issues/1271
• A new set of APIs: https://gitlab.com/gitlab-org/gitlab-ee/issues/1228
• Integration in Issue board: https://gitlab.com/gitlab-org/gitlab-ee/issues/1265
• Ability to define number of days in a week, and number of hours in a day https://gitlab.com/gitlab-org/gitlab-ee/issues/1272
• Recognize the word Time in slash commands so we list all the ones related to time tracking https://gitlab.com/gitlab-org/gitlab-ee/issues/1281

Awesome that you are adding/extending time tracking features to gitlab.

It would be really great if it would be possible to connect the time spent to a date. This would allow to generate reports for checking how much time was reported per day or week and double checking if somebody forgot to report the time spent on one day.

I see Time Tracking being part of "Enterprise Premium", but in my opinion this should definitely be part of "Enterprise Starter" as both this and a burndown chart should be basic planning features

https://about.gitlab.com/products/

for Time Tracking in "EE Starter"

Basic time tracking (what we have as of 8.15) is coming to CE in 8.16 (https://gitlab.com/gitlab-org/gitlab-ce/issues/25517). Advanced features will remain in EE.

Moving basic features to CE always is great news, as then "advanced" time tracking features (like reporting) are worth their money

Basically always deciding to release basic features in CE directly will be "a marketing machine" for enterprise, and also deliver more "free testers".

+1. For example, I can work 4h in a day, 7h in the next day and that will not sum up to 11h during the course of two days in real life, but 1 day +3h, which makes no sense to me, since it doesn't matter how many real life days I work, it should only count 1d of work when it reaches real life 24h of summed work hours.

The way it currently is, it counts a entire work day after 8h of work, which is not true at all in real life for a lot of people that work:

1. More than 8h in a real life 24h day.
2. With flexible work hours. For example, 7h in a day, 6 in another.
3. More than 5 days a week, like holidays and weekends.

This is not intuitive at all, since in real life 1d = 24h and 1 week = 7 days. As it currently stands, it's only useful for traditional companies employees with fixed work hours and fixed work days, for everybody else, this is useless.

"Ability to define number of days in a week, and number of hours in a day" would be immensely helpful and make this useful for everyone, not just a group of people.

I'm having the same problems as mentioned above by @cristianovitorino , this fixed format of 1d = 8h is impractical for many people

Why is this an EnterpriseEdition feature, when CommunityEdition has time tracking included in the features???