Skip to content
kumo

Tasks

Everything the studio does is a task on one board: features, art, bugs, playtest feedback, funding applications. Open it from Tasks.

The board shows the project’s tasks in columns, one per stage. From its toolbar:

  • New task.
  • Sprints: plan a sprint, and read its velocity and cumulative flow.
  • Email: the project’s secret address; a mail sent to it becomes a task (Email in).
  • Task from selection: one task for several selected items.
  • Team: who is on the project.

Select several cards to change them together. On a phone the board turns a column at a time, and a card’s details open in the card at the bottom.

A task opens on its sections, in this order unless your studio changes it:

SectionWhat it holds
FieldsType, stage, owner, dates, estimate, and your studio’s own fields
DescriptionWhat the task is, written like any page
ReferencesImages and links the work is based on
Voice-overThe lines to record, where the task has any
MediaPictures, video and sound attached to it
FilesSharePoint, OneDrive and Google Drive files (Office files)
ReviewIts versions and their verdicts (Review)
TestingTest runs and the builds they ran on
AssetsThe engine assets the work touches
TimeTime logged on it
WikiThe concepts it belongs to
CommentsThe conversation about it

Pull and merge requests linked to a task show on it with their state.

A task type (a feature, a character model, a bug, a funding call) carries its own stages, fields and checklist. Types and their templates are kept in Tasks → Production → Templates. A template inherits from another, so a change to Character reaches Hero character too.

Any kind of item, a task, a milestone, a product, a person, can carry the studio’s own fields. A field can be a formula over the others, the way a spreadsheet cell is.

A formula can read anything the studio keeps, through any chain of links:

  • A task’s assignee and the assignee’s lead, so assignee.lead.specificity works.
  • All the task’s assignees at once, as a list: SUM(assignees.hours).
  • The records that point back at an item. A person reads their tasks as linked.task.assignees.title.
  • Any of the studio’s data, such as HR records (linked.hr_record.person.title) or time off.

A link field connects items however your studio works: a person’s lead, a task’s reviewers, a milestone’s owner. A field’s Only where rule gives it to just the items it fits: CONTAINS(groups.discipline, "Concept Art") gives a person field only to concept artists.

A number can keep a range, lowest to highest in steps, and is then a slider.

Who sees its values narrows a field to the person themself (for a task, its assignees), one of the studio’s groups, or whoever holds a permission. Its values are kept apart and reach only those people’s devices. A formula that reads such a value is seen only by them too, unless the field says who sees it. That’s how a brief’s length can be shown to everyone while the preference behind it stays private. The same holds for the studio’s data: a value from an HR record reaches only the people who may read that record.

A task template’s Brief sets how its tasks’ briefs are written. Its length and the number of open questions are formulas over the task, so they can follow who the task is for. A stage’s hand-over field can have an Only on tasks where rule, so it’s asked for only on the tasks it fits.

For example, give people a private Preferred specificity from 1 to 5, seen only by themselves. Then on the generic task template set:

  • Length, in words: COALESCE(assignee.specificity, 3) * 80
  • Open questions, at most: 6 - COALESCE(assignee.specificity, 3)

Each artist’s briefs then follow their own preference. Nobody else sees it, and the value itself is never sent to the assistant.

Tasks → Automations holds what happens on its own: when a task reaches a stage, a bug lands or a build finishes, run the next steps. A trigger’s rule reads everything a task’s formulas read, its assignee’s fields too, so a step can pick a template by who the task is for. A value only some people see decides whether the trigger fires, but it is never written into anything a step makes. A task’s Run an automation button starts one by hand. Builds are automations too, run on a build computer (Builds & release).