M-PM-1 (superseded): Vikunja project baseline — covered by existing init #26
Labels
No labels
blocked:needs-decision
bug
chore
cron
design
in-progress
infra
milestone
module-o
needs-decompose
needs-research
ops-task
pm
quickfix
security/medium
triage-approved
vikunja
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Mark/org_mode#26
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
CLOSED — SUPERSEDED (2026-08-21)
Vikunja project baseline (one project per org_mode repo, kanban view per
project, webhooks → daemon) is already implemented and live via
vikunja-project-init.sh(idempotent), the seeded kanban views, and theevent-driven webhook wiring documented in
docs/operational/daemon-routing.md.The Vikunja↔kanban sync bridge (
vikunja-kanban-synccron) is out of scope anduntouched. No build required. Reconciled in
docs/vikunja-pm-system.md.M-PM-1: Vikunja project baseline — init, kanban views, webhooksto M-PM-1: Vikunja project baselineM-PM-1: Vikunja project baselineto M-PM-1 (superseded): Vikunja project baseline — covered by existing init