Files
TimeTracker/docs/QUICK_FIX.md
Dries Peeters e4789cc26e feat: Add telemetry and analytics infrastructure with observability stack
Implement comprehensive analytics and monitoring system with PostHog integration,
complete observability stack (Prometheus, Grafana, Loki, Promtail), and CI/CD
workflows for automated builds.

Features:
- Add PostHog telemetry integration with privacy-focused event tracking
- Implement installation flow for opt-in telemetry configuration
- Add telemetry management UI in admin panel with detailed transparency
- Track key user events across all major features (projects, tasks, timer, etc.)

Infrastructure:
- Set up Prometheus for metrics collection
- Configure Grafana for visualization dashboards
- Integrate Loki and Promtail for log aggregation
- Add separate analytics docker-compose configuration

CI/CD:
- Add GitHub Actions workflows for building and publishing Docker images
- Implement separate dev and production build pipelines
- Configure automated image publishing to registry

Documentation:
- Restructure documentation into organized docs/ directory
- Add comprehensive guides for telemetry, analytics, and local development
- Create transparency documentation for tracked events
- Add CI/CD and build configuration guides

Code improvements:
- Integrate telemetry hooks across all route handlers
- Add feature flags and configuration management
- Refactor test suite for analytics functionality
- Clean up root directory by moving docs and removing test artifacts

Breaking changes:
- Requires new environment variables for PostHog configuration
- Docker compose setup now supports analytics stack

Changes: 73 files changed, 955 insertions(+), 14126 deletions(-)
2025-10-20 14:38:57 +02:00

2.2 KiB

Quick Fix for Kanban Columns Error

The Problem

The kanban_columns table doesn't exist in your PostgreSQL database, causing the error:

relation "kanban_columns" does not exist

Quick Solution (2 minutes)

Run these commands:

# Step 1: Enter your Docker container
docker exec -it timetracker_app_1 bash

# Step 2: Run the migration
cd /app && alembic upgrade head

# Step 3: Exit and restart
exit
docker-compose restart app

That's it! Your application should now work.

Alternative: Manual SQL (if alembic fails)

# Connect to database
docker exec -it timetracker_db_1 psql -U timetracker -d timetracker

# Paste this entire block
CREATE TABLE IF NOT EXISTS kanban_columns (
    id SERIAL PRIMARY KEY,
    key VARCHAR(50) NOT NULL UNIQUE,
    label VARCHAR(100) NOT NULL,
    icon VARCHAR(100) DEFAULT 'fas fa-circle',
    color VARCHAR(50) DEFAULT 'secondary',
    position INTEGER NOT NULL DEFAULT 0,
    is_active BOOLEAN NOT NULL DEFAULT true,
    is_system BOOLEAN NOT NULL DEFAULT false,
    is_complete_state BOOLEAN NOT NULL DEFAULT false,
    created_at TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP,
    updated_at TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP
);

CREATE INDEX IF NOT EXISTS idx_kanban_columns_key ON kanban_columns(key);
CREATE INDEX IF NOT EXISTS idx_kanban_columns_position ON kanban_columns(position);

INSERT INTO kanban_columns (key, label, icon, color, position, is_active, is_system, is_complete_state)
SELECT * FROM (VALUES
    ('todo', 'To Do', 'fas fa-list-check', 'secondary', 0, true, true, false),
    ('in_progress', 'In Progress', 'fas fa-spinner', 'warning', 1, true, true, false),
    ('review', 'Review', 'fas fa-user-check', 'info', 2, true, false, false),
    ('done', 'Done', 'fas fa-check-circle', 'success', 3, true, true, true)
) AS v(key, label, icon, color, position, is_active, is_system, is_complete_state)
WHERE NOT EXISTS (SELECT 1 FROM kanban_columns LIMIT 1);

\q

# Exit and restart
docker-compose restart app

Verify It Worked

# Check the table
docker exec -it timetracker_db_1 psql -U timetracker -d timetracker -c "SELECT COUNT(*) FROM kanban_columns;"

Should return: count: 4

Done! Navigate to /tasks and your kanban board will work with custom columns.