Docs / Working in Kevta / Tasks & fields

Tasks & fields

A task is the unit of work in Kevta. Open one from any view and you get the same editor — as a full page at its own URL, or as a panel docked beside the board.

Anatomy of a task#

Every task has three parts.

A title. The only required field, up to 120 characters. Click it to rename in place.
A description. Rich text — headings, lists, bold, italic, underline, links, code and inline images. Up to 15,000 characters of text.
Properties. Everything else lives in the right-hand rail: status, priority, who it is for, when it is due, and any field your board has added.

If your board has task keys switched on, the task also gets a short identifier such as KEVTA-28. That key is its permanent handle: it appears in the URL, it is what you quote in conversation, and Copy branch name turns it into a ready-made Git branch.

Properties#

This is the part of Kevta worth understanding early: status, priority, assignee and due date are not fixed built-in fields. They are properties defined on the board, and a new board simply arrives with a sensible set already created. A board admin can rename them, recolour their options, add new ones, or remove the ones you do not use.

Properties are managed in Settings → Columns & fields on the board, via New property. Seven types are available:

Property types

TextFree-form text.

NumberA numeric value — useful for your own estimate scale.

DateA calendar date.

CheckboxTrue or false.

UserOne or more workspace members — this is what an assignee field is.

SelectOne option from a list you define, each with a colour.

Multi-selectAny number of options from that list.

Settings marks each property Built-in or Custom. Built-in properties are the ones the board was seeded with; they cannot be renamed or deleted, which keeps the views and integrations that depend on them working. A property's type is fixed once it exists — to change a Text field into a Select, add a new property.

Status#

Status is a Select property, so its options are yours to shape. New boards start with five:

To Do, In Progress, In Review, Ready for QA, Done

Add, rename, recolour and reorder these in Settings → Columns & fields. The order you put them in is the order columns appear on the board and the order tasks sort in.

Kevta recognises a finished task by its status name. Names containing done, complete, closed, resolved or shipped count as finished — that is what draws the green check and fills in sub-issue progress. A status containing cancel is deliberately not counted as finished. Rename your final column to something unrelated and those cues stop working, so keep a recognisable word in the name.

Priority#

Priority is also a Select property. New boards start with Low, Medium and High, and you can add your own.

Kevta styles and sorts priorities by name: options containing urgent or critical sort first and render with a warning icon, then high, then medium or normal, then low. Anything it does not recognise still works — it simply sorts last and renders neutrally.

Labels#

Labels are a separate, board-level set of coloured tags — independent of properties. Create and edit them in Settings → Labels, then apply any number of them to a task from its rail. Label names are unique within a board.

Sub-issues#

A task can contain other tasks. In the Sub-issues section you can either type a title to create a new child, or link an issue that already exists. Kevta shows how many children are finished, and each child links back to its parent in the breadcrumb.

Sub-issues are ordinary tasks, so they have their own key, properties and comments — they are not lightweight checklist items.

Blocking relationships#

Beyond parent and child, Kevta models one kind of dependency, in both directions: a task can block another, and is therefore blocked by it. Add either from the Relationships section; recording one direction automatically gives you the other.

When a task is blocked, a banner on the task says so, which is the point — the blocker is visible without going looking for it.

Comments & activity#

Comments use the same rich-text editor as the description, and you can edit or delete your own. Below them, the feed records what has happened to the task — status moves, property changes, relationship edits and more.

The feed opens on Comments so discussion is not buried in field changes; switch to All for the full history. Comments from other people appear as they are posted, without a refresh.

Description history#

Kevta keeps previous versions of a task's description. Open the revision menu to see earlier versions, compare one against the current text, and restore it if the edit was a mistake. Useful when a long-lived ticket gets rewritten and you need the original wording back.

Watching a task#

Watch on a task subscribes you to it, so you hear about activity on work you care about without being assigned to it. The button reads Watching once you are subscribed; press it again to stop. See notifications for where the resulting updates land.