New

Map repositories to projects for agent time

An admin can now say which project and task each repository's agent time belongs to, so nobody has to add a file to a repository before its sessions are recorded.

Under Settings → Agent time → Repositories, an admin or owner maps a git repository to a project and task. Paste the remote in any form: the SSH and HTTPS addresses of a repository are the same rule.

A rule can cover every branch, or only branches matching a pattern such as release/*. A branch rule beats the every-branch rule, and the narrower of two patterns wins. The page has a check that shows which rule wins for a remote and branch.

A .timetrakkr.json file in a repository still works, and overrides the rule for that repository.

What this does not do:

  • A repository with no rule is still not tracked. The plugin matches the rules on your own machine and sends nothing, not even the repository's name, for one that is not mapped.
  • You are only told about projects you can log time to. If your workspace restricts members to assigned projects, a rule for a project you are not on does not reach you.
  • It does not move agent time already recorded. A changed rule applies to sessions that start afterwards.

The assistant can list the rules, check what a remote maps to, and set or remove a rule, for admins and owners.

← Everything that has changed

The hours, the invoices, and what they earned

Free for unlimited people. One paid plan, $10 per member per month, when you want HR, scheduling, timesheet approvals, scheduled backups, email from your own domain and scheduled reports.

Start free