Integrations
Use GitLab integration when you need to connect commits to planned work
GitLab integration connects development activity with the work you plan and review.
Problem / use case
If you need to connect commits to planned work, GitLab integration becomes fragile when the work behind open GitLab when the feature is enabled. and Connect the relevant repository or activity source. is separated from Progress, Reports analytics, and Daily Plan.
What should be done conceptually
GitLab integration works best when the integrations decision, next action, and progress evidence stay close enough for connect commits to planned work to remain visible.
TimeLens solution
TimeLens solves that by making GitLab integration part of the same workspace as Progress, Reports analytics, and Daily Plan, so the feature helps the work move instead of becoming another isolated page.
Actual app screen
The public guide links to the real TimeLens route instead of showing a recreated mockup. Open the linked TimeLens screen to see the same route in action.
Actual product snapshots
How to use it in TimeLens
Open GitLab when the feature is enabled.; Connect the relevant repository or activity source.; Use Progress and reports to connect code work back to tasks and time.
What it helps with
Connect commits to planned work; Review product-building effort; Keep engineering context close
Where this feature connects
Progress; Reports analytics; Daily Plan; Feature access settings
Open this in TimeLens
Open the matching TimeLens menu item after signing in, or create an account to start from the same workspace.
Related feature pages
Continue with the most relevant TimeLens guide pages for this workflow.
Progress · Reports analytics · Daily Plan · Settings: Access