- Add Linear import (GraphQL, personal API key, optional team key filter).
- Centralize integration HTTP via integration_session and session_request.
- Add integration_sync_context for project/task refs and custom_fields metadata.
- Refactor Asana, GitHub, GitLab, Jira, Trello, ActivityWatch, and QuickBooks to use helpers.
- Extend integration UI, settings, and scheduled sync behavior as needed.
Unify buttons, cards, headers, toasts, and form treatments across the app so screens feel consistent and are easier to scan on desktop and mobile. Update the broader template set to use the shared UI primitives and responsive spacing patterns introduced in this refresh.
Display formats for dates and times now follow the system settings (Admin
settings) by default. Users can override in their profile (User settings) or
choose "Use system default" so their view matches the rest of the system.
Backend:
- User.date_format and User.time_format are nullable; null means use system.
- Migration 120 makes these columns nullable (existing rows unchanged).
- get_resolved_date_format_key() and get_resolved_time_format_key() in
timezone utils return the effective key (user or system) for templates and API.
- Context processor injects resolved_date_format_key and resolved_time_format_key
so base.html and JS (window.userPrefs) always see the resolved format.
- User settings form: "Use system default" option and save logic for null.
- User.to_dict() includes resolved date_format, time_format, and timezone for
API clients (e.g. mobile).
Web:
- base.html uses resolved keys for window.userPrefs (no hardcoded fallback).
- Replaced display-only strftime() in templates with |user_date, |user_datetime,
|user_time, and |format_date so all visible dates/times respect settings.
Left <input type="date"> values and URL/API params as YYYY-MM-DD where required.
Mobile:
- ApiClient.getCurrentUser() and user prefs provider load resolved prefs from
/api/v1/users/me.
- date_format_utils maps API keys to intl patterns; formatDate, formatTime,
formatDateTime, formatDateRange used for display.
- Time entries screen (filter dialog), time entry form, time entry card, and
home dashboard use user prefs for formatting; API requests still send ISO dates.
Co-authored-by: Cursor <cursoragent@cursor.com>
Import window and web activity from a local ActivityWatch aw-server
(https://activitywatch.net/) as automatic time entries (source='auto').
- Add ActivityWatchConnector: test_connection, sync_data, get_config_schema
- Per-user integration; config: server_url, default_project_id, lookback_days,
optional bucket_ids (default: aw-watcher-window_* and aw-watcher-web_*)
- No OAuth; setup at /integrations/activitywatch/setup
- Idempotent sync via IntegrationExternalEventLink and external_uid
- Register connector; treat activitywatch as per-user in IntegrationService
- activitywatch_setup route and template; connect redirect and is_global updates
- View/manage: Configure and Edit Configuration links for activitywatch
- docs/integrations/ACTIVITYWATCH.md; tests for connector and idempotency
Fix multiple issues with CalDAV calendar integration:
Error Handling & User Experience:
- Fix 'Integration not found' error after saving CalDAV configuration
- Improve error handling in view_integration route to gracefully handle missing/invalid credentials
- Add connector error display in integration view template with helpful links
- Fix 'Test Connection' button always showing errors by improving credential validation
- Add better error messages for SSL, timeout, and connection errors with actionable guidance
Sync Improvements:
- Fix sync returning 0 items with no feedback - now provides detailed messages
- Add support for DURATION-based events (not just DTEND)
- Improve sync result messages to distinguish between 'no events found' vs 'all events already imported'
- Add synced_items field for compatibility with scheduled sync tasks
- Better handling of duplicate UID race conditions during import
CalDAV Client Enhancements:
- Improve XML parsing error handling with clear error messages
- Handle empty responses gracefully (return empty multistatus for no events)
- Add time range validation in fetch_events
- Better error handling in calendar discovery with step-by-step error messages
- Improve iCalendar parsing with better error logging
Configuration & Setup:
- Add auto_sync configuration option in CalDAV setup form
- Add URL validation for server_url and calendar_url
- Ensure credentials are properly saved and integration marked as active
- Improve CalDAV setup route to handle missing credentials during initial setup
Logging & Debugging:
- Add comprehensive logging throughout sync process
- Log calendar discovery steps and event fetch operations
- Better error context in logs for troubleshooting
This addresses user-reported issues where:
- Users couldn't click on integration after saving
- Test Connection always failed with generic errors
- Sync showed 0 items with no explanation
- Credentials weren't being saved properly
This commit implements a comprehensive refactoring of the integration system to support both global (shared) and per-user integrations, adds new integrations, and improves the overall architecture.
Key changes:
- Add global integrations support: most integrations are now shared across all users (Jira, Slack, GitHub, Asana, Trello, GitLab, Microsoft Teams, Outlook Calendar, Xero)
- Add new integrations: GitLab, Microsoft Teams, Outlook Calendar, and Xero
- Database migrations:
* Migration 081: Add OAuth credential columns for all integrations to Settings model
* Migration 082: Add is_global flag to Integration model and make user_id nullable
- Update Integration model to support global integrations with nullable user_id
- Refactor IntegrationService to handle both global and per-user integrations
- Create dedicated admin setup pages for each integration
- Update Trello connector to use API key setup instead of OAuth flow
- Enhance all existing integrations (Jira, Slack, GitHub, Google Calendar, Asana, Trello) with global support
- Update routes, templates, and services to support the new global/per-user distinction
- Improve integration management UI with better separation of global vs per-user integrations
- Update scheduled tasks to work with the new integration architecture
This commit introduces a comprehensive integration framework and multiple new features to enhance the TimeTracker application's capabilities.
Major Features:
- Integration Framework: Extensible system for third-party integrations with support for Jira, Slack, GitHub, and calendar services
- Project Templates: Reusable project templates for faster project creation
- Invoice Approvals: Workflow for invoice approval before sending
- Payment Gateways: Online payment processing integration with Stripe support
- Scheduled Reports: Automated report generation and email delivery
- Custom Reports: Advanced report builder with saved views
- Gantt Chart: Visual project timeline and dependency management
- Calendar Integrations: External calendar synchronization with Google Calendar support
- Push Notifications: Enhanced notification system with PWA support
Bug Fixes:
- Fix None handling in analytics routes
- Fix dynamic relationship loading issues in ProjectRepository and ProjectService
- Fix parameter ordering in service methods
- Fix None duration_seconds handling in budget forecasting
UI/UX Improvements:
- Update logo references to timetracker-logo.svg
- Add favicon links to all templates
- Add navigation items for new features
- Enhance invoice view with approval status and payment gateway links
Database:
- Add Alembic migrations for new features (065, 066, 067)
Dependencies:
- Add stripe==7.0.0 for payment processing
- Add google-api-python-client libraries for calendar integration
Dries Peeters