Activate/deactivate pipeline for a week

What this does: Toggles the active status of a pipeline week. When a week is marked as active, the planned tasks are automatically transferred to each team member’s personal stack (Kanban board) in the correct order. This is typically done after the weekly pipeline planning meeting when all tasks have been agreed upon.

How it works:

• Creates a PipelineMeta record if it doesn’t exist for the week (sets ready=true)
• If PipelineMeta already exists, toggles the ready boolean value
• The week is determined from the start date using ISO week numbering
• Dates should be in ISO format (YYYY-MM-DD)

Status meanings:

• 🟢 Active (ready=true): Current approved planning, tasks are visible in employee stacks
• 🟠 Inactive (ready=false): Draft for the upcoming week, still being planned

Required Permission: Pipeline.canChangeSettings

Use cases:

• Mark a week as active after completing weekly planning meetings
• Deactivate a week to make changes to the planning
• Automate the activation process as part of a planning workflow

curl -X POST "https://leadtime.app/api/public/tasks/pipeline/status" \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
  "dateEnd": "2025-11-16",
  "dateStart": "2025-11-03"
}'

const response = await fetch("https://leadtime.app/api/public/tasks/pipeline/status", {
  method: "POST",
  headers: {
    "Authorization": "Bearer YOUR_ACCESS_TOKEN",
    "Content-Type": "application/json"
  },
  body: "{\n  \"dateEnd\": \"2025-11-16\",\n  \"dateStart\": \"2025-11-03\"\n}"
});

import requests

response = requests.post(
    "https://leadtime.app/api/public/tasks/pipeline/status",
    headers={
        "Authorization": "Bearer YOUR_ACCESS_TOKEN",
        "Content-Type": "application/json"
    },
    data="{\n  \"dateEnd\": \"2025-11-16\",\n  \"dateStart\": \"2025-11-03\"\n}",
)

{
  "success": true
}