Venom Tasks planning
Plan work in Venom Tasks with projects, milestones and updates, a drag-to-reschedule timeline, team cycles with a burn-up chart, saved views, and team and workspace settings.
Venom Tasks is the issue tracker inside Venom Cloud. This page covers the planning side: projects, the timeline,
cycles, saved views and settings. Issues, boards, the inbox and the ⌘K menu have their own page. Every planning page
is under /tasks and opens for members of an organisation that has the Venom Tasks add-on (see
The add-on).
Projects
/tasks/projects lists every project, grouped by status: planned, in progress, paused, completed and canceled.
Each row shows:
- the teams that own the project (by team key);
- its health from the latest update: on track, at risk or off track;
- its lead;
- its target date, in red once it has passed;
- a progress bar.
Progress counts estimate points. An unestimated issue counts as 1 (or 0, when its team turns Count unestimated issues as one point off), and canceled issues drop out of the scope. The
solid part of the bar is completed work and the lighter part is work in progress. New project (or n then p)
asks for a name, an overview, a status, a lead, start and target dates and the owning teams.
Layouts, filters and display
The switch in the header shows the projects as a List, a Board or a Timeline (⌘/Ctrl+B flips between
list and board). On a phone the switch sits in the filter row and the board scrolls sideways.
- Filters: Filter (or
f) adds a chip: status, status type (not started, in flight, closed), priority, health (including "no update"), lead, members (the lead counts as one), creator, labels, teams, lead team (a project's first team), initiative, milestones, start date, target date, name and summary, or one project. Sets take is, is not and, for labels, members, teams and initiatives, includes all of; each value shows how many projects it would keep. Dates take no date, has a date, overdue (target date only), within the next or last 7, 30 or 90 days, or before or after a day.Shift+Fremoves the last chip andAlt+Shift+Fclears them. The chips are in the page's link (?pf=), so a filtered list can be shared, and the timeline shows the same filtered projects. - Display (or
Shift+V): group by status, status type, lead, members, team, lead team, priority, labels, health, initiative, start month or target month, or not at all; sub-group the list one more level. A project with several members, labels, teams or initiatives shows in each of their groups, and projects with none of them come last under "No …". Order by manual order (the default), target date, start date, name, priority, progress, health, created or updated, and reverse any of them but manual order. Completed projects keeps completed and canceled projects from the last week, month (the default) or year, all of them, or none. Properties picks what each row shows: milestones, summary, priority, status, health, teams, lead, members, start, target, issues, progress, created, updated, completed and labels. Reset goes back to the defaults. Venom remembers the display in your browser. - Board: a column per group (status unless you pick another grouping). Drag a card to another column to set its status, lead or priority; a health board is read-only, since health comes from updates. Empty columns fold into Hidden columns and open while you drag.
- In place: click a row's status, priority, lead, labels, teams, members, start or target to change it there. In manual order, drag a row onto another to move it.
- Selection:
xselects the focused project, Shift-click selects a range, ⌘/Ctrl-click adds one and⌘/Ctrl+Aselects every project shown. The bar at the bottom sets the status, lead, priority or labels of all of them, adds them to an initiative, or archives them. Esc clears the selection.
Every change saves at once and is put back with a message if the server refuses. The toast's Undo (or ⌘/Ctrl+Z)
reverts the last change, a whole bulk change in one step. The list draws only the rows near the screen, so it stays
fast with hundreds of projects. "Make default for everyone" is not there yet: the display is per browser.
On the focused project (or the selection), and on a project's page: p then n adds it to an initiative, p then
m changes its members, p then t its teams, p then l its labels, ⌘/Ctrl+Alt+S sets the start date,
⌘/Ctrl+Alt+D the target date, and ⌘/Ctrl+U opens its updates. On the list ⌘/Ctrl+. copies its ID,
⌘/Ctrl+Shift+, its link and ⌘/Ctrl+Shift+' its name, and Alt+F adds it to your favorites.
/tasks/projects/{id} is one project, with four tabs:
- Overview: the project's description in Markdown (click it, edit, save with ⌘Enter), progress, and the milestones. Each milestone has its own target date, completion percentage and progress, and the next unfinished one is marked; milestones are renamed, described and reordered by drag (Milestones). The latest update is shown underneath, and below it the project's documents.
- Issues: the project's issues, grouped by milestone. Drop an issue on a milestone to move it there.
- Activity: every change to the project, newest first: who created it, renamed it, changed its status, priority, lead, dates, members, labels or summary, posted an update or added a milestone.
- Updates: status posts. Pick a health, write what changed, and post with ⌘Enter. The newest post sets the project's health on the list. An update an agent posted through MCP says so. Updates can be edited, deleted, discussed and reacted to, open with a summary of what changed, and follow an update schedule that reminds the lead (Project updates); the ⋯ menu's Update schedule… sets it.
Details panel
Under the name sits a one-line summary. The Details button in the page header shows or hides a panel on the right (Venom remembers your choice). It holds every property, edited in place: Status, Priority (urgent, high, medium, low or none), Lead, Members (people working on it besides the lead), Dates (start to target), Teams, and Labels (workspace labels, the ones no single team owns). Below are the milestones with their progress and the five latest activity entries; See all opens the Activity tab. A priority can also be set in the header row.
Teams takes teams in place: pick one from the list to add it, × to remove it. A project can belong to several teams, and it can hold issues of teams it doesn't list. A private team you are not in is never shown, and changing the teams leaves it on the project.
Move a project to another team
Move to team… under the Teams row replaces the project's teams with the one you pick (private teams you can't see stay). Move its issues in other teams too (on by default) also moves the project's issues that are in other teams to that team, by the same rules as moving an issue: each gets a new identifier and the old one keeps working, the status maps by name or type, team labels map by name or are removed, the cycle is cleared, the estimate is kept if the new team's scale has it. The issues stay in the project, and issues of the new team's subteams stay where they are. Turned off, the issues stay in their own teams. The dialog says how many issues move and, before you confirm, what they lose.
Milestones, updates, members, documents and the project's own address stay. A large project moves its issues in
batches of 100 and the dialog counts them as they go; if the page closes part way, Move again finishes the rest.
The activity says "moved the project from CON to VEN". Over MCP: tasks_project_move (and teamIds on
tasks_project_update to add or remove teams); over HTTP: POST /tasks/api/projects/{id}/move
(API).
Documents
The Overview lists the project's Documents: notes of the org vault in Venom Notes, with their
title, last editor and date. Click one to open it in Notes. New document makes a note named for the project in
Projects/<project name>/ whose first line links back to the project; it needs the org:manage permission, as the org
vault does in Notes. Link existing note searches the org vault and attaches any note you pick. Remove detaches
a document from the project and keeps the note. The section is hidden when the org has no Notes add-on.
Status, lead, dates and health are edited in the page header and save at once. A failed save is put back with a message.
Timeline
/tasks/projects/timeline draws each project as a bar from its start date to its target date, coloured by status,
with its progress filled in. A project with no target date gets a two-week bar from its start. Canceled projects
are left out. Each dated milestone of a project is a diamond on its row at the milestone's target date (filled once
all its issues are done); hover it for the name, date and progress.
- Drag a bar to move both dates, or drag either end to change only that one. Releasing the bar saves the new
dates, and the toast's Undo (or
⌘Z) puts the old ones back. A click without a drag opens the project. - Filters: the timeline is the projects list's third layout, so the list's filter chips (and
f) apply to it too. - Zoom by week, month, quarter or year, with the buttons or the keys
w,m,qandy;=and-step in and out, and⌘+scroll (Ctrl+scroll off a Mac) zooms one step around the pointer, keeping the day under it in place. Today (or.) scrolls back to today. - From the keyboard:
jandkmove between projects;→and←step through the projects and their milestones in order (a project, then its milestones by date, then the next project);Alt+→andAlt+←move the focused project or milestone a day,Alt+Shift+→andAlt+Shift+←a week;Enteropens the project,xselects the focused bar or milestone andEscapeclears.{hides or shows the project list on the left. - Milestones: drag a diamond to move its date;
Shift+drag moves the project's later milestones with it. Right-click a project's row and pick Add a milestone on … to make one on that day. - Display (the button beside the zoom): Group by initiative, team (a project's first team), lead or status.
A project in two initiatives shows under both, marked
+1; the empty group ("No initiative") comes last. Click a group's header, or presston one of its projects, to fold it. Show cycles of a team shades that team's cycles behind the bars and names them in the header, the current one a little stronger. Show dependencies turns the lines off and on. The timeline remembers these choices for you in this browser.
Project dependencies
A project can block another: the blocked project should start on or after the day its blocker is due.
- Add or remove one from a project's details panel (Dependencies → Add under Blocked by or Blocking, × to
remove), from the project page's ⋯ menu or the command menu with the project open (Blocked by…, Blocking…:
every project, the current ones checked, a click toggles one), from the timeline's right-click menu on a row (the
same two rows), or on the timeline by dragging from the small
circle at a bar's end to another bar ("this blocks that"); from the circle at the start, the other bar blocks this
one. Dropping on empty space or pressing
Escapecancels. Every add and remove has Undo. - Lines run from the blocker's end to the blocked project's start. They are grey while the plan holds and red
when the blocked project starts before its blocker is due, and the blocked bar gets a warning sign; the details
panel says by how many days. A line is dashed when either project is missing a date. Hover a line to see both
projects and the gap; click it to select it and press
Backspaceto remove it (you are asked first). - Moving a chain: dragging a bar later also moves the backlog and planned projects it blocks, only as far as they
need to start on or after their blocker's new target (a dashed ghost shows where they will go).
⌘+drag moves the project alone;Shift+drag moves it and every project it blocks by the same number of days, whatever their status. Completed and canceled projects never move, projects without dates are skipped, and each project's milestones move with it. The whole move is one save and one Undo. - No loops: a dependency that would close a loop (Atlas blocks Beacon blocks Atlas, or through a third project) is refused with a message naming the loop.
- Privacy: a dependency on a project you can't see (only in a private team you are not in) is never named. The panel and the bar show a lock with how many there are.
- Dependencies also show in both projects' Linked sections as blocks links. Agents use
tasks_projectdep_list,tasks_projectdep_addandtasks_projectdep_remove(theplanningtool set); the API is in the Tasks API.
Cycles
A cycle is a fixed-length sprint that a team schedules ahead automatically. Turn cycles on per team in its settings
(/tasks/settings/teams/{key}#cycles):
| Setting | Values |
|---|---|
| Length | 1 to 8 weeks |
| Starts on | any day of the week |
| Cooldown | none to 4 weeks between cycles |
| Scheduled ahead | 1 to 6 upcoming cycles |
| Roll unfinished work over | when a cycle ends, its open issues move into the next cycle |
| Add started issues to the cycle | see Cycle automation; off until you turn it on |
| Add completed issues to the cycle | see Cycle automation; off until you turn it on |
The form previews the dates of the next cycles before you save. A sub-team that follows its parent's cycle schedule follows these switches too.
/tasks/cycles (?team=KEY picks the team) shows the current cycle:
- its dates and days left;
- four figures: scope, started, completed and the completion rate;
- a burn-up chart: the scope line and the completed line by day (started too, when it was recorded), the target
(dashed), the projection (dotted, ending "On track" or "N days late") and capacity, with hover details per day,
←and→to step through days (read out with each day's numbers and target), and a table view of the same numbers (how they are computed); - its issues by state.
Count by issues or by estimate points when the team uses estimates. Complete cycle closes the current cycle
early and, if you choose, moves its open issues into the next one. Upcoming and past cycles are listed underneath.
/tasks/cycles/{id} opens any one of them. A cycle's description, when it has one, shows under its title and at the
top of its details sidebar.
Cycle automation
Two switches in the team's cycle settings put work into cycles without anyone doing it by hand. Both are off until a team turns them on.
- Add started issues to the cycle: an issue without a cycle that moves to a started status joins the current cycle. Between cycles (a cooldown) it joins the next one; when none is scheduled yet it stays without a cycle.
- Add completed issues to the cycle: an issue without a cycle that is completed joins the current cycle. Between cycles it joins the cycle that just ended.
An issue created straight into a started or completed status counts too. An issue that already has a cycle never moves, reopening an issue keeps its cycle, and a change that sets the cycle itself (to one, or to none) wins. Triage, backlog, unstarted and canceled never trigger it, and neither do issues brought in by an import. The issue's activity says added the issue to Cycle 12 automatically, by Venom Tasks. Cycle days are UTC days.
Start, end and edit a cycle
Each cycle's ⋯ menu (on its row and in its header) has:
- Edit cycle…: the name (empty shows as "Cycle N"), a description, and the dates its state allows: an upcoming cycle's first and last day, the running cycle's last day, none for a finished one. End a name in a number ("Sprint 40") and the cycles after it that are unnamed, or follow the old name, count on: Sprint 41, Sprint 42, and the cycles scheduled later too. Moving the last day into the next upcoming cycle moves that cycle's start (it can't take all of its days); overlapping any other cycle is refused.
- Start today… on the next upcoming cycle: the running cycle completes now and its open issues move into the one
you start (even when the team doesn't roll work over), or, between cycles, the next one simply starts today. Its end
date stays, as do the dates of the cycles after it. You confirm first; it can't be undone. The page's
⋯menu has the same as Start Cycle N today…. - End today… on the running cycle: it ends after today and completes in the next minute after midnight (UTC), rolling work over as the team's settings say. The next cycle keeps its start date, so there may be a gap.
"Today" in these pages is your own calendar day, in your browser's time zone: at 01:00 in Singapore, Start today
starts the cycle on that date, not on the UTC date (the day before), and the cycles list counts "starts in N days" and
marks the running cycle from your day. Projects' target dates ("Due today", "Overdue by 3 days"), the timeline's today
line and Pulse read your day too. When an agent or the API starts a cycle without a today, it is the day in the
time zone of your Tasks notification settings (delivery.timeZone), else your calendar's, else the UTC day. A
filter on the current, next or previous cycle uses that same day. The background work that completes, schedules and
snapshots cycles, and the auto-add rule above, still count UTC days.
Capacity
Each upcoming cycle in the list, and the header of the current or upcoming cycle, shows a small ring: what is planned in the cycle against what the team usually finishes, the average of its last three completed cycles (points when the team estimates, else issues), as the cycle's insights count it. Hover or focus it for "12 of ~15 points". Past 100 % it turns to the warning colour. A team with no completed cycle yet uses its people times the organisation's median finished per person per cycle; with neither, it says No history yet.
Calendar feed
Calendar feed… in the cycles page's ⋯ menu gives you an address to subscribe to in a calendar app (Google
Calendar, Apple Calendar, Outlook), or a one-off .ics download. It lists the team's last two completed cycles and
every one after them as all-day events, with each gap between cycles as a Cooldown event; an event's description
holds the cycle's description and its link.
The address is yours alone and works like a password: anyone who has it can read the team's cycle names, dates and descriptions (nothing else), so keep it private. Reset address makes a new one and the old one stops at once; Turn off stops it. It also stops answering as soon as you leave the organisation or can no longer see the team (a private team you were taken out of). Calendar apps refresh it every so often; the feed asks for at most every 15 minutes.
Cycle details
⌘I (Ctrl+I on Windows and Linux) or Details in the cycle's header opens the details sidebar beside it; the
same again, Esc inside it or Close hides it, and it stays open or closed in this browser. It holds:
- Progress: scope, started and completed now, with the percentage, in issues or points (the cycle's switch).
- The burn-up with its target, projection and capacity.
- Capacity: what is planned against the team's average over its last three completed cycles ("Planned 34 of ~28 points", in a warning colour when over), or a finished cycle's success.
- Breakdown by Assignees, Labels or Projects: each group's issues, how many are done, and its points.
Click a group to filter the cycle's issue list to it (a chip shows how many of the list's issues it keeps); click
it again, or
×on the chip, to clear it. Canceled issues are left out, as in the scope.
Drag its left edge to resize it (or focus the edge and use ←/→, Home and End; double-click resets). On a phone
it covers the screen.
Saved views
A view is a saved set of issue filters: team, state, assignee, delegate (agent), label, priority, project, cycle and
text. Filters you can only build in the filter bar, such as is not, due date and creator, are saved too and apply when the view opens. On a filtered issue list, Save view (or Alt+V) keeps the current filters under a name, with one of three
scopes:
- Only me: a personal view, which only you see;
- Team: shown to everyone under that team;
- Workspace: shown to the whole organisation.
Views appear in the sidebar under the workspace links. /tasks/views lists them all. You can rename or delete your own views, and admins can
manage shared ones. /tasks/views/{id} shows a view's filters in words and its issues, with a link that opens them
as a filtered list. Its Display button has the list's display options, starting from
the view's saved display; Save as default for this view stores the current ones on the view (PATCH /tasks/api/views/{id} with display), and Reset to default goes back to them. The filters live in the URL (?team=ENG&stateType=started&label=…), so a filtered list can also
be shared as a link.
Project views
The projects list saves views too. Filter it, pick a layout, grouping and properties, then press Save
view (or Alt+V): the view keeps the filter chips and the display. Opening it shows the projects list with them;
change either and Update view stores the change on the view (its owner or an admin). Changing the display on a
view's page doesn't change your own projects list. /tasks/views has two tabs, Issues and Projects, and the
sidebar marks project views with the project icon.
A view's menu
The ⋯ beside a view (on /tasks/views and in a view's header) has:
- Notify me… (issues views): When issues are added, When issues are completed or canceled, Both or Off. See Following a view.
- Edit view…: name, description, who sees it, the team, and for a team view Show as a tab.
- Duplicate view: a personal copy named "… (copy)", owned by you, with the same kind, filters and display.
- Change owner… (team and workspace views): hand the view to another member. The owner or an admin can do it. A view's header says who owns it ("Owned by Ana"); the creator owns it at first.
- Copy link: the view's address. A link opens the view only for people who can already see it.
- Delete view (its owner or an admin): asks first, and says how many people follow it.
Following a view
Notify me… puts a notice in your Tasks inbox when issues join an issues view, when its issues are completed or canceled, or both. It is off until you turn it on, per view and per person.
- Changes are batched: a view is checked at most every five minutes, and everything that happened in between becomes one notice per view ("3 issues joined ‘Bugs this week’", "closed in ‘Bugs this week’").
- Your own changes never notify you, even if someone else changed the same issue too.
- The view's query runs as you, so you only hear about issues you can open. If you lose access to the view or its private team, the notices stop.
- Issues that join only because time passed (a filter such as "due this week") are not announced; the view's members are re-read quietly once a day. Turning notifications on, or coming back after more than a day without changes being read, starts from what the view shows then, without a burst of old notices.
- A view whose filter no longer runs shows This view needs attention in its header, and nobody is notified until it is fixed.
- Push and email for these notices follow your Status and priority changes switches in notification settings.
Team views as tabs
A team view with Show as a tab turned on appears after the team's own tabs (Triage, Issues, Active, Backlog, Active cycle). Drag a tab onto another to move it (its owner or an admin); the order is the views' order. On phones the tabs scroll in the row above the list. A tab view's page shows the same row of tabs.
Lists of issues by identifier
/tasks/issues/{ids}, such as /tasks/issues/ENG-1,ENG-7,OPS-3, lists exactly those issues, in that order, up to 100. Issues that don't exist or
that you can't open are counted ("2 more not found or not yours to see") but never named. Agents read the same issues
with tasks_issue_get, one identifier at a time.
Team settings
/tasks/settings/teams/{key} has one section per topic:
- General: the team's name and key. The key prefixes issue identifiers (
ENG-42). It is 1 to 7 characters: capital letters and digits, starting with a letter. Renaming the key renumbers nothing, and links to the old identifiers keep working. - Workflow: the states an issue moves through, grouped by type (triage, backlog, unstarted, started, completed,
canceled).
- Add a state to any type, rename it in place, pick its colour, change its type, and reorder states within a type.
- Every team keeps at least one state of each required type.
- Deleting a state that issues use asks where those issues go.
- Here you also pick the state new issues start in and turn triage on or off. The Triage type is offered only while triage is on.
- Labels: the team's own labels and label groups. An issue takes at most one label from each group.
- Estimates: the scale and three switches (see Estimates).
- Cycles: the settings in Cycles.
- Members: who is on the team, as admin or member, with the members of the teams above it ("from a parent team"). Agents can be members too, so that issues can be delegated to them. Members are managed in Settings → Teams.
Changing settings needs the team's admin role (an admin of a team above it counts) or an org role that manages Tasks (owner or admin). Everyone else sees the team page read only.
Estimates
The scale is one of: none, linear (0–5), Fibonacci (0, 1, 2, 3, 5, 8, 13, 21), exponential (0, 1, 2, 4, 8, 16, 32) or T-shirt sizes (XS 1, S 2, M 3, L 5, XL 8). Under it are three switches:
- Extended scale (off for every team until turned on) adds the scale's extra values: T-shirt XXL (13) and XXXL (21), exponential 64. A team that moved in from Linear also keeps here the extended values Linear sent for its issues that Tasks' scale lacks (see Estimates in Move in). The switch says what it adds.
- Allow zero estimates (on unless turned off) offers 0 for work too small to count. T-shirt has no 0.
- Count unestimated issues as one point (on unless turned off): an issue without an estimate weighs 1 point in project, cycle and initiative progress, the cycle's scope, burn-up, velocity and capacity, and project insights. Off, it weighs 0 in all of them at once. A project with issues of several teams weighs each issue by its own team's switch. Insights' Effort measure sums estimates only, so it is the same either way.
Turning a switch off or picking another scale never changes an issue: an estimate the team no longer offers stays on the issue, shown as it is ("21 (outside the scale)" in its menu, or XXXL on T-shirt), and the section says how many issues hold one. The estimate menus and the API offer and take only what the team offers now (the API answers 400 to anything else, except the value an issue already has). A subteam that uses its parent's estimates takes the scale and all three switches, and follows them when the parent's change.
API and MCP: estimateExtended, estimateAllowZero and countUnestimated (booleans) on POST and
PATCH /tasks/api/teams and on tasks_team_create and tasks_team_update; a team also carries estimateExtra (the
values kept from a move-in), and GET /tasks/api/teams/{id} answers estimatesOutside, how many of its issues hold an
estimate it does not offer now.
Workspace settings and the add-on
/tasks/settings lists the teams, the workspace labels and label groups that every team shares, and everyone an
issue can go to; subteams are listed under their parent and private teams carry a lock. New team there creates
a team: a name, a key (suggested from the name: "Mobile Apps" gives MA), an optional Parent team (it becomes a
subteam), Private, and an estimate scale (Fibonacci unless you pick another; change it later in the team's
settings). The team starts with the default workflow, and you become its admin. A top-level team needs owner or
admin; a parent team's admins add subteams to it. Or add a team from Settings → Teams adds an org team that is not
in Tasks yet (it keeps its name, key, members and place in the tree).
A team whose scale is none takes no estimates: the issue's estimate menu says so, and the API answers 400 to an estimate on its issues.
The workspace page also lists:
- Members are the people of the organisation. Invite them in Venom Cloud's own members settings.
- Agents are MCP clients and Venom daemons. Issues are delegated to them, not assigned.
The Plan card shows the Venom Tasks add-on as billing sees it:
- included, when billing is off on the deployment;
- in preview, when every organisation has it;
- on, as part of the organisation's subscription;
- not on yet, with a link to Billing, where an admin adds it.
While the add-on is off, the Tasks API answers 403 addon_required and the pages say so.
Dependencies
Dependencies in the sidebar (/tasks/dependencies) draws every issue that is in a blocks relation, across all
of the organisation's teams. Blockers sit on the left and an arrow points to the issue they block.
Above the graph, each open Urgent (P0) issue that an open issue still blocks is listed with how many issues are
behind it, how many hops deep the chain goes and which teams it crosses. The issues and arrows on those chains are
drawn in the warning colour. Tick Only chains to an Urgent issue to hide the rest. A completed or canceled issue
no longer blocks, so a chain stops there and it is drawn faded. Click an issue to open it. Add the relations on an
issue's page (Blocks or Blocked by); the graph reads them from GET /tasks/api/dependencies.
Keyboard
| Where | Keys | Does |
|---|---|---|
| Projects | j / k, Enter |
move, open |
| Projects | n then p |
new project |
| Projects | f, Shift+F, Alt+Shift+F |
add a filter, remove the last, clear them |
| Projects | x, ⌘A, ⌘B, Shift+V |
select, select all, list or board, display options |
| Projects | ⌘., ⌘⇧,, ⌘⇧' |
copy the focused project's ID, link, name |
| Projects and a project | p then n / m / t / l |
initiatives, members, teams, labels |
| Projects and a project | ⌘⌥S, ⌘⌥D, ⌘U |
start date, target date, updates |
| Project | p then s, p then a |
change status, change lead |
| Project | ⌘⇧U |
write an update |
| Timeline | w m q y, = -, ⌘+scroll |
zoom |
| Timeline | . |
go to today |
| Timeline | → ← |
step through projects and milestones |
| Timeline | Alt+← Alt+→, Alt+Shift+← Alt+Shift+→ |
move the focused project or milestone a day, a week |
| Timeline | {, t, Backspace |
hide the project list, fold the group, remove the selected dependency line |
| Issue lists | Alt+V |
save the filters as a view |
? opens the shortcuts panel, the planning keys included; its This page switch shows the keys that work on the page you are on, that page's own first.