MokoConsulting/MokoGitea-APP
1
0
Fork 0
Code Issues 158 Pull Requests 5 Releases 96 Wiki Activity

feat: Dolibarr time tracking sync #55

New Issue
Open
opened 2026-05-08 04:47:36 +00:00 by jmiller · 0 comments
jmiller commented 2026-05-08 04:47:36 +00:00
Owner
Copy Link
Copy Source

Bi-directional time tracking between Gitea and Dolibarr.

Gitea to Dolibarr

  • When time is logged on a Gitea issue, push to linked Dolibarr task
  • Map Gitea user to Dolibarr user
  • Include issue title as time description

Dolibarr to Gitea

  • Time entered in Dolibarr reflects on linked Gitea issue
  • Webhook from Dolibarr on time entry creation

API

  • POST /repos/{owner}/{repo}/issues/{index}/times (exists) — enhanced to auto-sync to Dolibarr
  • GET /repos/{owner}/{repo}/dolibarr/timesheet?from=&to= — aggregated report

Dashboard

  • Widget showing time tracked per client/project
  • Billable vs non-billable breakdown
  • Export for invoicing
Bi-directional time tracking between Gitea and Dolibarr. ## Gitea to Dolibarr - When time is logged on a Gitea issue, push to linked Dolibarr task - Map Gitea user to Dolibarr user - Include issue title as time description ## Dolibarr to Gitea - Time entered in Dolibarr reflects on linked Gitea issue - Webhook from Dolibarr on time entry creation ## API - `POST /repos/{owner}/{repo}/issues/{index}/times` (exists) — enhanced to auto-sync to Dolibarr - `GET /repos/{owner}/{repo}/dolibarr/timesheet?from=&to=` — aggregated report ## Dashboard - Widget showing time tracked per client/project - Billable vs non-billable breakdown - Export for invoicing
Sign in to join this conversation.
Labels
Clear labels
breaking-change
Breaking API or behavior change
 ci-cd
CI/CD pipeline changes
 config
Configuration changes
 dependencies
Dependency updates
 deploy-failure
Deployment failed
 docker
Docker/container changes
 documentation
Documentation changes
 good first issue
Good for newcomers
 health-check
Repo health check result
 help wanted
Extra attention needed
 mokostandards
Related to MokoStandards framework
 push-failure
Git push operation failed
 security
Security vulnerability or hardening
 size/l
200-500 lines changed
 size/m
50-200 lines changed
 size/s
10-50 lines changed
 size/xl
500+ lines changed
 size/xs
< 10 lines changed
 standards-drift
Deviates from MokoStandards
 standards-update
MokoStandards compliance update
 sync-failure
Sync or mirror failed
 tech-debt
Technical debt and TODO/FIXME items
 upstream
upstream
Inherited from upstream Gitea
 work-in-progress
Draft or incomplete work
No labels
Priority Medium
Type Feature
Status —
Priority —
Type —
Milestone
No items
No Milestone
Assignees
Clear assignees
jmiller (Jonathan Miller) moko-deploy (Moko Deploy Bot)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/MokoGitea-APP#55
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?