Togra — Technical Overview
What's under the hood
A detailed look at the Togra project management platform — its sprint model, workflow engine, ideas canvas, team role system, and integration architecture.
Sprint Board
Five states, full visibility
The Togra sprint board models work as it actually flows — from planned through blocked to done — with views that surface the right information for each team member.
Five-State Kanban
Tasks progress through To Do → Ready → In Progress → On Hold → Done. Each state transition is explicit and tracked, giving a precise history of how each piece of work moved through the sprint.
Swimlane by Team Member
The Members view renders the sprint board as swimlanes — one row per team member. Each lane shows that person's tasks across all five columns, making individual capacity and blockers immediately visible.
Stories View
The Stories view groups tasks by the backlog story they belong to. See all tasks for a given story in one place, with their workflow stage shown alongside the sprint Kanban state.
Sprint Metadata
Each sprint has a defined date range and a story count. Sprint headers display the active date window and total in-scope stories, giving the team a shared context for the planning horizon.
Task Assignment
Tasks within a sprint are assigned to named team members. Assignments are visible on every task card and reflected in the swimlane view — no ambiguity about who owns what.
On Hold Tracking
The On Hold column provides explicit visibility into blocked work. Tasks that can't progress — waiting on an external dependency, a review, or a decision — have a home that is visible to the whole team.
Story Model
Stories with built-in workflow
Every backlog story in Togra can carry a visual workflow that defines the stages it must pass through from start to done. Story progress is tracked at the workflow level, not just the Kanban column.
Workflow per Story
Each story is linked to a workflow — a directed graph of stages such as Write Up, Refine, Select for Work, Implement, Test, Deploy, and Archive. The active stage, pending stages, and completed stages are all visible on the story detail view.
Active Path Visualisation
The workflow graph renders with colour-coded paths: active (green), pending (grey), and loop-back (orange) edges. Team members can see at a glance where a story sits in its lifecycle and what comes next.
Role-Assigned Stages
Each stage in a story workflow is assigned to one or more team roles. When a stage becomes active, the team members in that role are responsible for advancing it — no manual hand-off coordination required.
Story Points
Stories carry a story point estimate for velocity tracking. Points are visible on sprint boards, backlog views, and team assignment views — supporting sprint planning and capacity management.
Story Notes
Context that stays with the work
Story notes in Togra are a full document workspace — not just a comment thread. Notes are versioned, organised into folders, and can include assets from the Comad media library.
Versioned Notes
Each note saves a timestamped version every time it is edited. The history of a note — who wrote what, and when — is preserved alongside the story, providing a complete record of how requirements and decisions evolved.
Personal and Shared Folders
Notes are organised into folders: My Notes (private to the author) and Shared (visible to the whole team). Team members can keep working notes private while sharing polished decisions and requirements with collaborators.
Rich Text Editing
The note editor supports headings, lists, checklists, emphasis, and embedded references. Write up requirements, acceptance criteria, and decisions in a format the whole team can read and act on.
Workflow Link
Notes are directly linked to the story's associated workflow. When a story note is open, the workflow diagram is visible in the same panel — so the work context and the process stage are always in view together.
Ideas Board
A canvas for structured thinking
The Togra ideas board is a free-form canvas for team brainstorming — built on the same visual graph engine as story workflows and Obair process design.
Infinite Canvas
Ideas are positioned freely on a zoomable, pannable canvas. Zoom out for a full project overview; zoom in for the detail of a specific idea cluster. Pan, zoom, and minimap controls are always available.
Typed Idea Cards
Ideas come in typed variants — Folk Stories, Skeptics, and custom types — each with its own colour. Card types make it easy to distinguish different kinds of thinking on the same canvas and filter for what matters.
Connections and Flow
Draw directional connections between ideas to show relationships, sequences, and dependencies. Connections are colour-coded and can loop back — the same graph model used in story workflows.
Comad Asset Embedding
Idea cards support embedded images and media from the Comad Digital Asset Manager. Browse your asset library from within the ideas canvas and insert reference images directly into the card where they belong.
Team & Roles
The right work to the right people
Togra models your team structure explicitly. Roles are assigned to projects, members are assigned to roles, and work is assigned to roles — so the right tasks always reach the right people.
Project Roles
Each project defines a set of roles — Architect, Developer Backend, Developer Frontend, Product Manager, and any custom roles needed. Roles are the unit of work assignment in story workflows and sprint task allocation.
Member Assignment
Team members are assigned to one or more roles within a project. The Team view lists all members with their active task count and role assignments — giving project leads a clear picture of team composition and workload.
Task Visibility by Member
Clicking any team member in the Team view shows all tasks currently assigned to them across the project — story name, task name, sprint, status, start date, end date, and duration — in a single table.
Multi-Role Members
A team member can hold multiple roles in the same project. A developer who also performs code review can be both Developer and Architect — and will receive tasks assigned to either role as stories progress through their workflows.
Comad Integration
Assets where you need them
Togra and Comad are designed to work together. Browse your digital asset library without leaving Togra, insert images and documents directly into story notes and idea cards, and keep your media linked to the work that uses it.
In-App Asset Browser
A built-in Comad media picker opens from the note editor and ideas canvas. Browse by collection, search by name or type, and see thumbnails and file metadata — all without leaving the Togra interface.
Collection Navigation
Assets are organised by Comad collection — British Royal Family, Clann Family Tree, Business, Music, People, Sport, and any collection in your library. Navigate the same hierarchy you use in Comad directly from Togra.
AI Basket
The Comad picker includes an AI Basket — a curated set of assets selected by the Comad AI for relevance to the current context. When writing about a topic, the AI surfaces the most relevant assets from your library automatically.
Shared Asset Context
Both Togra and Comad share the same Ullav authentication infrastructure. The asset picker uses the same JWT token as the rest of the platform — no separate login or API key required to access your library from within a story.
Technical FAQs
Technical questions answered
What is the technology stack?
Togra is built with Next.js 16, React 19, and TypeScript. The UI uses Tailwind CSS and the visual workflow and ideas board use ReactFlow (@xyflow/react) for the graph canvas. The backend is a Rust service (Axum) with PostgreSQL for persistence. Authentication is via the shared ullav-user-management JWT service.
How does Togra relate to the Obair workflow engine?
Story workflows in Togra use the same directed graph model as Obair business process workflows. The visual editor, stage types, role assignments, and active-path tracking are shared concepts. Teams that outgrow Togra's project management model can extend their workflows with Obair's full automation, MCP integration, and enterprise scale features.
How does the Comad integration work technically?
Togra calls the Comad REST API to browse collections and retrieve asset metadata and thumbnails. The same JWT bearer token used throughout the Ullav platform authenticates the request — no additional credentials are needed. Asset URLs returned by Comad are embedded directly into story note content.
Does Togra support multiple projects?
Yes. Togra supports multiple independent projects, each with their own team, roles, backlogs, sprints, and ideas boards. Project navigation is available from the top-level Projects view. Users see only the projects they are members of.
What languages does Togra support?
The Togra web application supports English, Irish (Gaeilge), and German via next-intl. The language can be switched from the top navigation bar. All UI elements, labels, and system messages are fully translated for each supported locale.
How is Togra deployed?
Togra deploys as a Docker container with a Helm chart for Kubernetes, following the same deployment model as the rest of the Ullav suite. It connects to PostgreSQL for persistence and to the ullav-user-management service for authentication. Sensitive configuration is managed via Docker secrets or Kubernetes secrets — never baked into the image.
Ready to get organised?
Get in touch to discuss how Togra can be deployed and tailored to your team's needs.