joseph/internal-joseph
1
0
Fork 0
Code Issues 21 Pull requests Projects Releases Packages Wiki Activity Actions

[OneDev #20] research(workflow): standalone team Kanban board — independent of Planner/AT/OneDev #24

New issue
Closed
opened 2026-05-24 04:46:39 +00:00 by joseph · 1 comment
joseph commented 2026-05-24 04:46:39 +00:00
Owner
Copy link

Imported from OneDev issue #20 (id 35397)
Original project: internal-joseph
Original state: Closed
Original submitterId: 5
Original submitDate: 2026-04-17T17:21:16.222+00:00
Original lastActivity: {'date': '2026-04-18T13:08:09.028+00:00', 'description': "changed state to 'Closed'", 'userId': 5}

Original fields:

  • Type: New Feature
  • Priority: Normal
  • Assignees: None

Idea

A self-hosted Kanban board for the PCT team that doesn't depend on Microsoft Planner, Autotask, or OneDev. Cards, columns, drag-and-drop — simple and fast. Could be an off-the-shelf tool deployed to pctbin.com or a lightweight custom build integrated into the existing stack.

Why

Planner has write-permission blockers (k1-dataverse#1), AT is ticket-centric not task-board-centric, and OneDev boards are dev-facing. A neutral team Kanban removes the tool friction for non-dev staff tracking work.

Open questions

  • Off-the-shelf (Planka, Focalboard, WeKan) vs custom build?
  • Auth: Dex SSO or open internal?
  • Does it need AT ticket integration, or truly standalone?
  • New repo or extend an existing hub tool?
Imported from OneDev issue #20 (id 35397) Original project: internal-joseph Original state: Closed Original submitterId: 5 Original submitDate: 2026-04-17T17:21:16.222+00:00 Original lastActivity: {'date': '2026-04-18T13:08:09.028+00:00', 'description': "changed state to 'Closed'", 'userId': 5} Original fields: - Type: New Feature - Priority: Normal - Assignees: None ## Idea A self-hosted Kanban board for the PCT team that doesn't depend on Microsoft Planner, Autotask, or OneDev. Cards, columns, drag-and-drop — simple and fast. Could be an off-the-shelf tool deployed to pctbin.com or a lightweight custom build integrated into the existing stack. ## Why Planner has write-permission blockers (k1-dataverse#1), AT is ticket-centric not task-board-centric, and OneDev boards are dev-facing. A neutral team Kanban removes the tool friction for non-dev staff tracking work. ## Open questions - Off-the-shelf (Planka, Focalboard, WeKan) vs custom build? - Auth: Dex SSO or open internal? - Does it need AT ticket integration, or truly standalone? - New repo or extend an existing hub tool?
joseph commented 2026-05-24 04:46:48 +00:00
Author
Owner
Copy link

Imported from OneDev comment id 379 on issue #20
Original userId: 5
Original date: 2026-04-18T13:08:08.028+00:00

Implemented as Vikunja on VMID 137 (tasks.pctbin.com). Deployed 2026-04-17/18.

What was done:

  • Vikunja v2.3.0 + Postgres 16 on Docker Compose, pve1 VMID 137
  • Caddy vhost + Dex SSO (vikunja client registered)
  • Project: PCT Internal Dev — List/Gantt/Table/Kanban views, Backlog→In Progress→Done columns
  • Labels: bug, feature, infra, bdd-scenario
  • PCT Team created (public, self-join) — shared with project at write level
  • All 13 Pester tests green; topology.json + deps.json updated in infrastructure repo

Remaining (filed separately): OIDC auto-team-join via vikunja_groups claim requires a claims-enrichment layer between Dex and Vikunja — Dex+M365 can't produce that claim natively.

Imported from OneDev comment id 379 on issue #20 Original userId: 5 Original date: 2026-04-18T13:08:08.028+00:00 Implemented as Vikunja on VMID 137 (tasks.pctbin.com). Deployed 2026-04-17/18. **What was done:** - Vikunja v2.3.0 + Postgres 16 on Docker Compose, pve1 VMID 137 - Caddy vhost + Dex SSO (vikunja client registered) - Project: PCT Internal Dev — List/Gantt/Table/Kanban views, Backlog→In Progress→Done columns - Labels: bug, feature, infra, bdd-scenario - PCT Team created (public, self-join) — shared with project at write level - All 13 Pester tests green; topology.json + deps.json updated in infrastructure repo **Remaining (filed separately):** OIDC auto-team-join via vikunja_groups claim requires a claims-enrichment layer between Dex and Vikunja — Dex+M365 can't produce that claim natively.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
joseph/internal-joseph#24
No description provided.