Skip to content
Docs menu

Initiatives in Venom Tasks

Group projects under an initiative, nest initiatives, and read their roll-up, timeline and status updates, with keys for each.

View .md

Initiatives is in the Tasks sidebar under Workspace, next to Projects, Cycles and Insights.

Initiatives

An initiative is a goal that groups projects, as in Linear. Open Initiatives at /tasks/initiatives.

  • The list shows initiatives as a tree under their status: Active, Proposed, Planned, Completed, Canceled. A sub-initiative sits under its parent whatever its own status; a chevron folds a row's sub-initiatives, and what you folded is remembered on this device. Each row shows the health of its latest status update, its owner, the target date (red when overdue), a progress bar and how many projects it holds, sub-initiatives' included.
  • New initiative asks for a name, a description (markdown), a status, an owner, a target date and, when there are others, which initiative it is part of. Press ⌘↵ to create it. A new initiative starts as Planned; Proposed is for a goal nobody has agreed to yet.
  • An initiative's page (/tasks/initiatives/{id}) has three tabs: Overview, Timeline and Updates. The Overview holds its properties (change any of them in place), the Part of path above it, the Active projects bar, the description, its sub-initiatives and its projects.

Sub-initiatives

An initiative can sit under another: a company goal holds team goals, and its numbers count everything underneath.

  • Add sub-initiative… on the page (or n then s) picks an existing initiative to move under this one, or creates a new one by typing its name. The Part of field on any initiative moves it under another, or back to the top.
  • The page shows Part of Company › Platform above the tabs, each name a link. If a parent is archived, the path says so; archiving a parent never archives its sub-initiatives.
  • Limits. An initiative cannot sit under itself or one of its own sub-initiatives (initiative_cycle), and the tree is at most five levels deep, counting the moved initiative's own sub-initiatives (initiative_too_deep). Both come back as 400 with a sentence. The database enforces them too, so two people moving initiatives at the same moment cannot make a loop.
  • Deleting an initiative moves its sub-initiatives up one level, to its parent (or the top). They keep their projects; nothing is deleted but the initiative itself, and its projects stay.

Roll-up

  • Active projects is one bar over the projects under the initiative and every sub-initiative below it, each project once, coloured by the health of its latest update: on track, at risk, off track, or no update. Hover a segment (or read the legend) for the counts; press a segment to list those projects. A project is active when it is not archived, completed or canceled; the line also says how many projects there are in all (not archived, completed and canceled ones too).
  • A project linked at two levels (in a parent and in its child) counts once in the parent. A project in two initiatives counts in both. A sub-initiative that is archived counts for nothing, but the ones under it still reach the parent.
  • Progress is rolled up across every issue in all those projects. Canceled and archived issues are left out, and issues count by estimate points (an unestimated issue counts 1, or 0 when its team does not count unestimated issues), as on a project. Only what you can see counts: a private team's issues, and projects whose teams are all private teams you're not in, are left out of your numbers and your lists, and their names never appear.
  • The numbers match the Projects list: filtering Projects by Initiative (and the issue filter's Initiative) also reaches the projects of that initiative's sub-initiatives.

Projects

Pick Add a project to attach one; × takes it off (the project itself stays). A project can be in several initiatives. Each project shows its own status, health, lead, target date and progress. Projects of sub-initiatives are listed below, under From sub-initiatives.

Timeline

The Timeline tab draws the initiative's projects with the same timeline as Projects, one block per initiative: the initiative's own projects first, then each sub-initiative's (and everything under it) under its own heading.

Updates

Choose a health (on track, at risk, off track), write a note in markdown and post it. The latest update sets the initiative's health. Turn on Include sub-initiatives and projects to merge their updates into the feed, newest first, each labelled with where it came from; the switch is remembered on this device. Off shows only the initiative's own updates.

Keys

On the Initiatives page the keys act on the focused row (j and k move, Enter opens, ← and → fold); on an initiative's page they act on that initiative. The full list is in Keyboard shortcuts:

Keys Does
s Change the status
n then o Change the owner
⌘/Ctrl+Alt+D Set the target date
Alt+F Favorite the initiative: it joins your sidebar Favorites
Shift+H Remind me about the initiative
⌘/Ctrl+U Open the Updates tab
⌘/Ctrl+Shift+U Write an update
n then s Add a sub-initiative
⌘/Ctrl+., ⌘/Ctrl+Shift+,, ⌘/Ctrl+Shift+' Copy the ID, the link, the name

A reminder on an initiative arrives in your bell, like one on a project, and a favorite is gone when the initiative is deleted.

  • Completing an initiative stamps the date; moving it back to Active clears it. Deleting one never deletes its projects.

Members who can read Tasks can read initiatives. Creating and changing them needs a role that can change Tasks.

Moving in from Linear brings the initiative hierarchy along, with each project under the initiative that links it (see Move in from Linear).

  • Pulse: the updates of every project and initiative you lead, own or follow in one feed, and a weekly digest. Follow on an initiative's page adds it to your Pulse.
  • Insights: charts of how work flows, on any list, board, project, cycle or saved view.
  • Workspace labels and members have their own settings pages, at /tasks/settings/labels and /tasks/settings/members.