These are capabilities already implemented in Worklane. Choose a section: every block describes a concrete working scenario and reserves space for a short demo.
Stages and transitions form a directed graph with branches, merges and returns. Every transition can check permissions and roles, require a comment or assignee, evaluate card fields and enforce WIP limits; the visual editor flags unreachable stages and broken connections immediately.
A project can have several boards with stage-bound columns, swimlanes, filters and safe drag and drop. Cards support Markdown, assignees and watchers, dates and reminders, tags, custom fields, estimates and time tracking, files, dependencies, subtasks and checklists; milestones add progress, forecasting, nesting and a roadmap.
Any domain event can be connected to a condition tree and an ordered action chain. Built-in actions cover notifications, webhooks, email, card creation, movement and updates, assignments, watchers, tags, comments, due dates and more, with data templates, delays, error handling and a run log.
An event or manual start moves through branches, switches, variables, loops, actions, error paths, waits and stops. Long waits are persisted across server restarts, while graph validation and execution budgets keep enabled flows free of broken links and infinite loops.
Commit, branch, pull request and deployment events are linked to cards through references such as PK-123 and added to the work history. A merge can move a card and add a comment automatically; GitHub, GitLab, Bitbucket, Gitea and generic providers are normalized into events available to automation.
Chats and topics connect with a one-time code, receive aliases and have their own reply rules. The bot publishes card and release events, sends automation messages, accepts commands and AI requests, and asks the user to confirm every AI-proposed change directly in Telegram.
One event can arrive in-app, by email, in Telegram, through Web Push, mobile push or webhook. Users enable channels globally and per event type, configure quiet hours in their own timezone and optionally receive a daily or weekly digest.
The nested page tree loads as it expands and supports Markdown, search, breadcrumbs, drag and drop, archiving and revision history. Pages and cards link in both directions, keeping documentation beside the work it describes.
An incident can be reported in one line, while similar-record search helps mark a recurrence instead of creating a duplicate. A recurrence increments its counter and reopens a closed incident; the queue supports triage, a timeline, ownership, analytics and conversion of the full history into a card.
A pipeline is made of ordered shell steps, parameters, variables and environment targets; secrets are encrypted and masked in logs. A runner pulls work over outbound long polling and is selected by labels and grants, while manual or automated runs expose live logs, step statuses, cancellation and history.
Subscriptions can be global, company-wide or project-scoped and accept exact events, prefixes and wildcards. Each event can have its own URL, headers and JSON template with preview; requests are signed with HMAC-SHA256, retried by policy and stored for manual redelivery.
A personal key is shown only at creation and stored as a hardened hash. Its read, write, admin and resource-management scopes can be constrained by company, expiry and IP/CIDR allowlist, then revoked with last-use and request statistics available for review.
A bot is a real company member with a normal role: it can be assigned, mentioned and recorded as a comment author and audit actor. It has no password or user session, only separate API keys with narrow scopes, expiry and IP allowlists; suspension revokes access while preserving its history.
The assistant uses an OpenAI-compatible API and receives permitted context from cards, boards, stages, tags, Wiki and open incidents. It can read, explain valid moves and propose changes to cards, Wiki and incidents, but checks the user’s real permissions and executes every mutation only after explicit confirmation.
Dashboards combine widgets for cards, deadlines, blockers, workload and metrics in the chosen project context. Inbox deduplicates assignments, overdue work, dependencies, reviews, mentions, notifications and invitations; profiles show member work, while global search and the command palette find entities across the system.
Gantt shows dates, dependencies, the critical path and milestones, while flow metrics calculate cycle time, lead time, throughput, the 85th percentile and CFD from event history. Estimation and velocity, capacity, burndown, calendar, dependency graph, releases, time, risks, workload, SLA, stand-ups and retrospectives are available alongside them.
A card, selection, Wiki page or incident can be opened through an unguessable guest link in an isolated shell without internal navigation. Links support expiry, one-time access, comment permissions and limits, a field allowlist and revocation; every open and action is checked server-side and audited.
System and custom roles combine granular permissions, individual grants and denials, and project overrides. Email verification, access recovery and revocable per-device sessions with refresh-token replay protection are backed by a unified audit trail that records the actor, action and context.
Open the app and start with a template, or draw your own workflow from an empty canvas. The demo company comes seeded with a branching process, five members and a board that already has history.
