Features
What Vorkhurry actually does
Nine groups of capability, every one of them built. Where something is only partly built, it says so — this page is generated from the same inventory the engineering team keeps.
Core project management
Projects, issues and the structures that hold them — the part of Vorkhurry people are in all day.
Projects
A project per stream of work, with its own key, members, milestones, epics, versions, components and labels.
/projects
Issues and subtasks
Create, update, assign, archive and delete issues; break one into subtasks; move it between projects or duplicate it wholesale.
/issues
Board
A drag-and-drop board per project, with columns from your own workflow statuses and swimlanes over them.
/projects/{id}?view=board
Backlog
The ordered queue of everything not yet in a sprint, ranked with lexorank so a reorder moves one row rather than renumbering the list.
/projects/{id}?view=backlog
List view
The same issues as a dense, sortable list when a board is the wrong shape for the question you are asking.
/projects/{id}?view=list
Calendar
Issues by date, for work whose deadline is the thing that matters.
/projects/{id}?view=calendar
Checklists
Named checklists on an issue, each with its own items and completion state.
Custom fields
Typed fields your organization defines, with options, attached to issues and searchable.
/settings/work
Planning
Deciding what happens next, and seeing whether it still fits.
Sprints
Plan, start and complete sprints. The commitment is snapshotted at start, so a sprint report reflects what was committed rather than what the scope became.
/projects/{id}?view=sprints
Gantt
A dependency-aware timeline per project: bars from start and due dates, milestones, progress, and finish-to-start arrows between blocked work.
/projects/{id}?view=timeline
Dependencies
Scheduling links between issues, resolved per project as the edge set the Gantt view draws — and checked for cycles.
Milestones and versions
Dated milestones and releasable versions per project, so a delivery date is a thing in the system rather than a line in a document.
Epics
A layer above issues, ordered within a project, that groups the work making up one deliverable.
Roadmap and initiatives
Initiatives sit above projects. One initiative reaches into epics in several projects, and its progress rolls up from them on every read rather than being stored and going stale.
/roadmap
Estimation and velocity
A configurable estimation scale per project, and a velocity series computed from completed sprints.
Team collaboration
The conversation around the work, kept next to the work.
Comments and reactions
Threaded comments on issues and other entities, resolvable, with reactions — and internal-only comments behind their own permission.
Attachments
Files uploaded straight to object storage through a pre-signed URL, then confirmed — the API never proxies the bytes.
Watchers
Follow an issue to be notified about it without being assigned to it.
Notifications
An in-app inbox with read, read-all and archive, per-user preferences, and a schedule for digests.
/notifications
Live updates and presence
A WebSocket channel per organization, project and issue: changes appear without a refresh, and you can see who else is looking.
Activity history
An append-only activity log per entity — who changed what, when, and from what to what.
Documents
Partly builtDocuments in folders with versions, restore and per-entity permission grants. The editor is plain text today, not a rich block editor.
/documents
Meetings
Scheduled meetings with attendees, responses, minutes and cancellation.
Development
The bridge between the issue tracker and the repository.
GitHub
Connected as a GitHub App, scoped to the repositories you install it on. Only the installation id is stored; every call mints a fresh token that expires in an hour.
/settings/integrations
Branch, commit and PR linking
Issue keys in a branch name, a commit message or pull-request text are matched against your own project keys and recorded as activity on those issues.
Pull-request transitions
Map a pull-request event to a status — opened to In Review, merged to Done. The move runs through the workflow's own guards, so a transition you have not allowed is skipped rather than forced.
Workflows and transitions
Issue types, statuses, priorities and the allowed transitions between them are your organization's data, not ours — edit them, reorder them, and the board's columns follow.
/settings/work
Personal access tokens
Scoped tokens for scripts and CI, issued and revoked from your own profile.
/settings/tokens
Outbound webhooks
Subscribe an endpoint to domain events and receive a signed payload, with a delivery log and a ping button to test it.
/settings/webhooks
Automation
Rules that do the repetitive part.
Automation rules
Trigger, condition and action rules that run on domain events, with a run history showing what fired and what it did.
Recurring issues
Rules that create an issue on a schedule.
Notification schedules
Batch notifications into a digest on a schedule instead of taking every event as it happens.
AI assist
Eleven assist actions on issues, projects and sprints — running on your organization's own provider account.
Issue assists
Draft a description, suggest acceptance criteria, break the issue into subtasks, summarise the thread, or suggest a priority with a one-line rationale.
Project assists
Draft a phased delivery plan, propose milestones, or identify delivery risks with impact and mitigation.
Sprint assists
Advise on sprint scope, write a stakeholder progress summary, or surface likely blockers and stalled work.
Your provider, your key
An administrator connects OpenAI, Anthropic or Google Gemini with the organization's own API key. There is no shared Vorkhurry key, and the key never leaves the server — the API returns a masked suffix only.
/settings/ai
Models, allow-lists and budget
Choose which models are enabled, set a default and per-feature overrides, and cap monthly spend. Every call is recorded, so usage is a number you can look at.
/settings/ai
Suggestions are reviewed, not applied
Output arrives as a suggestion you accept or reject. Applying it is a second, deliberate step — nothing a model wrote edits your issues on its own.
Reporting
Where the work actually is, measured rather than asserted.
Reports
Throughput, open work, cycle time and flow efficiency, with created-versus-completed flow and breakdowns by status category and priority.
/reports
Burndown and velocity
Per-sprint burndown and a velocity series per project.
Cumulative flow
A cumulative flow diagram per project, from daily rolled-up metrics.
Portfolio and workload
Progress across every project at once, and how work is distributed across the people doing it.
Search and saved filters
One ranked result set across issues, projects, epics, sprints, employees, documents, comments, meetings and announcements — permission-filtered inside the query, not after it. Save a filter and reuse it.
Time tracking
Partly builtLog work against an issue and read it back per issue. The timer, approvals and timesheet reports exist in the API but have no screen yet.
Organization and access
Who is in your workspace, what they can do, and the evidence of every change to that.
Organizations
Every account belongs to an organization — there is no path into Vorkhurry that produces a user without one. Slug, settings, verified domains and ownership transfer are all first-class.
/settings/organization
People, teams and departments
Employees, teams, departments, designations, skills and reporting lines, with an org chart computed from them.
/employees
Groups
Named groups of members, so access is granted to a set rather than to a list.
/settings/groups
Roles and permissions
146 permissions in a named catalogue, 20 role templates from Owner to Guest, per-member overrides, and an effective-permission view that answers what one person can actually do.
/settings/roles
Invitations
Invite by email with a role attached, preview an invitation before accepting, and revoke one that has not been used.
Audit log
An append-only record of settings changes, membership changes, role changes, permission overrides, invitations and ownership transfer — with the actor, the outcome, and what changed.
/settings/audit
HR module
Attendance, leave types, balances, requests and approvals, review cycles, performance reviews, announcements and policy acknowledgements.
Migration
Bringing work that already exists somewhere else.
Jira import
Pull issues from a Jira instance through its API.
/settings/import
Linear import
Pull issues from Linear through its API.
/settings/import
CSV import
Upload a file and map its columns — the path that works from anything.
/settings/import
Preview, map, validate, resolve
Every source record becomes a row with its own status, so an import is resumable, reports errors per row, and a re-run updates what it already created instead of duplicating it.
Start with your team, not with a sales call
Create a workspace, invite the people you work with, and bring your existing issues in from Jira, Linear or a CSV.