Work boards and tasks
Kanban boards with per-board ticket keys, item types, subtasks and epics, timelines, and links to conversations, feedback, and GitHub.
Work boards are where your internal work actually happens. They are a kanban system built into Hark, so a customer request or a ticket can become tracked engineering work without leaving the platform.
Boards, columns, and items
A work board has ordered columns (for example, To do, In progress, Done), and each column holds items. Columns can carry a work-in-progress limit to keep a stage from overloading. You drag items across columns as work progresses.
Ticket keys
Each board has a short key you choose when you create it (for example, ENG). Items on that board read as sequential keys like ENG-12, numbered per board. These keys are stable references you can drop into a commit message, a pull request title, or a branch name to link development work back to the item.
Item types and hierarchy
An item is a task, a bug, a feature, or an epic. Items support a hierarchy: a subtask points at its parent, and an epic's children point at it, so you can break a large piece of work down and roll it up. Items carry a priority, an assignee, a reporter, labels, and due and start dates.
Timeline and Gantt
Because items can carry a start date and a due date, boards offer a timeline (Gantt) view that places each item as a bar across its dates. This is how you see a plan across time rather than only a snapshot of columns.
Turning requests and conversations into work
An item can be promoted from a feedback post or converted from a conversation. This is the bridge from the customer side to the work side: a highly voted feature request becomes an item on your engineering board, and because the objects are linked, resolving the work can flow back to notify the customer who asked.
GitHub links
When you connect the GitHub integration, development signals attach to the item they mention. A commit, pull request, or branch whose message, title, or name contains an item key (for example, ENG-12) shows up on that item's development panel, with its state (open, closed, or merged) for pull requests. You can also create a branch or open a pull request straight from an item. See Integrations for setup.