GitLab has a nice feature called Time Tracking. You can record the time spent working on an issue or a merge request.
When I click the _Start timer_ button and then the _Stop timer_ button the time period should be added as _time spent_ to a corresponding issue or a merge request.
When I click the _Start timer_ button and then the _Stop timer_ button the time period isn't added as _time spent_ to a corresponding issue or a merge request.


No, this is not the expected behavior. They are two different functions. We do not want these messages clogging up our Gitlab issues:

If you want to integrate the two systems I suggest you use the Toggl and Gitlab APIs to push tracking info to Gitlab.
Would love for toggl to submit the time spent on the issue to the issue itself.
@emilv I would not completely agree with you, although you're completely right about:
They are two different functions.
Here is more about what the commenting on Gitlab really is/should be (IMHO it's really great that everything is logged - the flow is transparent).
I think @emilv, you want to filter some types of comments (they might blur a bit the view if you're working with issues/MR - agree). However, maybe developing the feature to filter the comments is better the way instead of suppressing nice new features? 馃槈
Thanks for all the input. I'll just add that if we were to implement a feature like this, it would probably be an opt-in setting.
Most helpful comment
Would love for toggl to submit the time spent on the issue to the issue itself.