Built for the Odoo you already run
No second account and no second source of truth. The app signs in with Odoo credentials, takes its task list from Odoo, and puts the hours back where the invoices are raised.
Authentication
People sign in with the Odoo server URL and the credentials they already use. There is no separate TimeTaskTracker account, so there is no separate list of users to keep in step when somebody joins or leaves.
Projects and tasks
The app reads the tasks assigned to that user and groups them under their Odoo project. Assign work in Odoo and it appears in the tracker; there is nothing to mirror by hand.
Timesheets
Stopping a session writes a timesheet line back to Odoo with the hours and the description. Project costing, billing and payroll read the same records they always did.
Discuss
Odoo channels and direct messages are available inside the app, with the Odoo 14, 15 and 16+ Discuss models detected automatically.
A tracker that does not sync is just a second spreadsheet
Most time trackers keep their own database and offer an export. That means somebody reconciles two sets of numbers at month end, and the one that gets invoiced is whichever was easier to reach.
Because TimeTaskTracker writes into Odoo as the work happens, the hours behind an invoice are the hours somebody actually logged, with a screenshot record and a written description attached to them.
- Odoo 14, 15 and 16+Version differences in the Discuss models are detected at runtime rather than configured.
- Your server, your dataThe app talks to your Odoo instance directly. There is no Squad Focus service in the middle holding a copy.
- Offline queueIf Odoo is unreachable, entries wait locally and post themselves when the connection returns.
- Live dashboardToday's hours are read back out of Odoo, so what the app shows and what Odoo holds cannot drift apart.
Already running Odoo?
Then most of the setup is done. Tell us your version and team size and we will take it from there.