# Taiga Project Management

> Agile project management platform for startups and teams.

- Category: Productivity & Collaboration
- Difficulty: advanced
- Components: taiga-gateway, taiga-front, taiga-back, taiga-async, taiga-events, postgresql, rabbitmq, redis
- Tags: agile, scrum, kanban, project-management, taiga
- Source: https://docker.recipes/productivity/taiga-pm

## Overview

Taiga is an open-source agile project management platform built specifically for multidisciplinary teams who want powerful project tracking without enterprise complexity. Born from the need for a modern alternative to heavyweight tools like Jira, Taiga combines intuitive design with robust functionality, supporting both Scrum and Kanban methodologies while maintaining the flexibility that startups and growing teams require. This comprehensive stack orchestrates seven specialized components: taiga-gateway handles HTTP routing and static file delivery, taiga-front provides the responsive Vue.js interface, while taiga-back serves the Django REST API that powers all project data operations. The architecture leverages PostgreSQL for reliable project data storage, RabbitMQ for asynchronous task processing, and taiga-events for real-time WebSocket communication that keeps team members instantly synchronized. The taiga-async worker processes background tasks like email notifications and file processing, while Redis could be added for session caching and performance optimization. This stack delivers enterprise-grade project management capabilities with the simplicity that agile teams demand, offering features like customizable workflows, time tracking, and comprehensive reporting without the overhead of traditional project management suites.

## Features

- Dual methodology support with native Scrum sprint planning and Kanban board visualization
- Real-time collaboration through WebSocket-powered live updates via taiga-events and RabbitMQ messaging
- Comprehensive issue tracking with user stories, tasks, bugs, and custom issue types with full lifecycle management
- Advanced project analytics including burndown charts, velocity tracking, and team performance metrics
- Flexible user role management with granular permissions for project owners, developers, and stakeholders
- Rich media support with file attachments, image previews, and document management through persistent volume storage
- RESTful API architecture enabling custom integrations and third-party tool connections
- Asynchronous task processing for email notifications, bulk operations, and background data processing

## Use cases

- Software development teams transitioning from Jira who need agile project management without licensing costs
- Startup engineering teams requiring integrated sprint planning, backlog management, and team velocity tracking
- Remote development teams needing real-time collaboration with live issue updates and team communication
- Consulting firms managing multiple client projects with separate workspaces and customized workflows
- Open source projects requiring public issue tracking with contributor management and community engagement features
- Educational institutions teaching agile methodologies with hands-on project management experience
- Small to medium agencies coordinating design and development workflows with client visibility and reporting

## Prerequisites

- Docker host with minimum 4GB RAM (PostgreSQL requires 1GB, RabbitMQ needs 1GB, remaining services need 2GB combined)
- Available ports 9000 for web interface and 5672/15672 for RabbitMQ management if external access needed
- Understanding of agile methodologies (Scrum/Kanban) and project management workflows for effective configuration
- Basic knowledge of environment variable configuration for database passwords and domain settings
- SSL certificate and reverse proxy setup if deploying for production use with HTTPS requirements
- SMTP server configuration details for email notifications and user invitation functionality

## docker-compose.yml

```yaml
services:
  taiga-gateway:
    image: nginx:alpine
    container_name: taiga-gateway
    ports:
      - "9000:80"
    volumes:
      - ./nginx.conf:/etc/nginx/conf.d/default.conf:ro
      - taiga-static:/taiga/static:ro
      - taiga-media:/taiga/media:ro
    depends_on:
      - taiga-front
      - taiga-back
      - taiga-events
    networks:
      - taiga-network
    restart: unless-stopped

  taiga-front:
    image: taigaio/taiga-front:latest
    container_name: taiga-front
    environment:
      - TAIGA_URL=${TAIGA_URL}
      - TAIGA_WEBSOCKETS_URL=${TAIGA_WS_URL}
    networks:
      - taiga-network
    restart: unless-stopped

  taiga-back:
    image: taigaio/taiga-back:latest
    container_name: taiga-back
    environment:
      - POSTGRES_DB=taiga
      - POSTGRES_USER=taiga
      - POSTGRES_PASSWORD=${DB_PASSWORD}
      - POSTGRES_HOST=db
      - TAIGA_SECRET_KEY=${SECRET_KEY}
      - TAIGA_SITES_DOMAIN=${TAIGA_DOMAIN}
      - TAIGA_SITES_SCHEME=http
      - EVENTS_PUSH_BACKEND_URL=amqp://taiga:${RABBITMQ_PASSWORD}@rabbitmq:5672/taiga
      - CELERY_BROKER_URL=amqp://taiga:${RABBITMQ_PASSWORD}@rabbitmq:5672/taiga
      - ENABLE_TELEMETRY=False
    volumes:
      - taiga-static:/taiga-back/static
      - taiga-media:/taiga-back/media
    depends_on:
      - db
      - rabbitmq
      - taiga-async
      - taiga-events
    networks:
      - taiga-network
    restart: unless-stopped

  taiga-async:
    image: taigaio/taiga-back:latest
    container_name: taiga-async
    entrypoint: ["/taiga-back/docker/async_entrypoint.sh"]
    environment:
      - POSTGRES_DB=taiga
      - POSTGRES_USER=taiga
      - POSTGRES_PASSWORD=${DB_PASSWORD}
      - POSTGRES_HOST=db
      - TAIGA_SECRET_KEY=${SECRET_KEY}
      - CELERY_BROKER_URL=amqp://taiga:${RABBITMQ_PASSWORD}@rabbitmq:5672/taiga
    volumes:
      - taiga-static:/taiga-back/static
      - taiga-media:/taiga-back/media
    depends_on:
      - db
      - rabbitmq
    networks:
      - taiga-network
    restart: unless-stopped

  taiga-events:
    image: taigaio/taiga-events:latest
    container_name: taiga-events
    environment:
      - RABBITMQ_URL=amqp://taiga:${RABBITMQ_PASSWORD}@rabbitmq:5672/taiga
      - TAIGA_SECRET_KEY=${SECRET_KEY}
    depends_on:
      - rabbitmq
    networks:
      - taiga-network
    restart: unless-stopped

  db:
    image: postgres:15-alpine
    container_name: taiga-db
    environment:
      - POSTGRES_USER=taiga
      - POSTGRES_PASSWORD=${DB_PASSWORD}
      - POSTGRES_DB=taiga
    volumes:
      - postgres-data:/var/lib/postgresql/data
    networks:
      - taiga-network
    restart: unless-stopped

  rabbitmq:
    image: rabbitmq:3-management-alpine
    container_name: taiga-rabbitmq
    environment:
      - RABBITMQ_DEFAULT_USER=taiga
      - RABBITMQ_DEFAULT_PASS=${RABBITMQ_PASSWORD}
      - RABBITMQ_DEFAULT_VHOST=taiga
    volumes:
      - rabbitmq-data:/var/lib/rabbitmq
    networks:
      - taiga-network
    restart: unless-stopped

volumes:
  taiga-static:
  taiga-media:
  postgres-data:
  rabbitmq-data:

networks:
  taiga-network:
    driver: bridge
```

## .env

```bash
# Taiga Project Management
TAIGA_URL=http://localhost:9000
TAIGA_WS_URL=ws://localhost:9000
TAIGA_DOMAIN=localhost:9000

# Secrets
SECRET_KEY=your_secret_key_here
DB_PASSWORD=secure_taiga_password
RABBITMQ_PASSWORD=secure_rabbitmq_password
```

## Usage notes

- Web UI at http://localhost:9000
- Default admin: admin / 123123
- Supports Scrum and Kanban
- Real-time updates via websockets
- Import from Jira, Trello, Asana

## Troubleshooting

- taiga-back failing with database connection errors: Verify DB_PASSWORD environment variable matches across taiga-back, taiga-async, and db services
- Real-time updates not working in web interface: Check that TAIGA_WEBSOCKETS_URL points to correct taiga-events service and RabbitMQ credentials match
- Static files (CSS/JS) not loading properly: Ensure taiga-static volume is properly mounted and nginx.conf routing is configured for /static/ paths
- Email notifications not sending from Taiga: Configure SMTP settings in taiga-back environment and verify taiga-async worker is processing mail queue
- RabbitMQ connection failures across services: Confirm RABBITMQ_PASSWORD is consistent and rabbitmq service is healthy before dependent services start
- High memory usage from PostgreSQL: Tune PostgreSQL configuration for your dataset size or increase container memory limits above 1GB minimum

