Skip to main content
Two column types help you plan work: Waits for, which links items, and Time tracking, which records the time spent.

​
Waits for

A Waits for column lets an item wait for other items on the same board. When one finishes late, the rest can move with it.
  • When you add the column, you choose the board’s Timeline column whose dates it moves. One Timeline can serve several Waits for columns.
  • Choose the items an item waits for, from 1 to 50. An item cannot wait for itself, and a link that would make a loop is refused (dependency_cycle).
  • Only Work writes the column: a plain cell edit, a form, an import or a type change cannot set it. Use the cell editor, PUT /v1/items/{id}/dependencies or boardy_set_dependencies.

​
Shift the dates that follow

Work looks at the end date. When you change a Timeline’s end date, and the Timeline is paired with a Waits for column, a prompt asks: Shift N dependents, Only this item or Cancel. If you shift, every item that waits for it, and every item that waits for those, moves by the same number of days (earlier or later). Each keeps its length.
  • An item with no dates is skipped, but the items that wait for it still move. An archived item never moves and nothing passes through it.
  • A shift is refused whole if it would touch more than 500 items or move more than 3,650 days. A board can have up to 10,000 linked items.
  • If more items wait than the app showed you, Work asks again instead of moving more than you agreed to.
  • All dates move together, in one change. After a move, Undo puts every date back.
  • The API is POST /v1/items/{id}/reschedule. With dryRun: true it shows the plan and writes nothing. Agents use boardy_reschedule_item.
Links are finish-to-start only. There is no lag, no other link type, and no link across boards. If a predecessor is deleted, its id stays in the cell until you edit it, and readers ignore it.

​
The Gantt view

A Timeline view becomes a Gantt when the board has a Waits for column. It draws an arrow between two bars when both items are in the view and have dates. An item with no dates, or one that a filter hides, has no arrow. Editing a bar’s dates behaves like editing the Timeline cell, including the prompt above.

​
Time tracking

A Time tracking column records sessions (who worked, from when to when) and an optional estimate, so an item shows time spent against time planned.
  • Tap play to start your own timer, and tap again to stop it. Each person has one running timer per cell, and many people can run theirs at the same time.
  • Add time by hand with a start and an end. A session lasts at most 24 hours, ends after it starts, and cannot end in the future.
  • Set an estimate, from 1 second to 10,000 hours, or clear it.
  • You can remove your own sessions. You can also remove a session that an Agent logged.
  • An item holds up to 300 sessions.
  • Everything you do is saved as you, never as someone else. A Write grant is not a licence to start or stop another person’s time.
The item shows the total, the estimate and the total for each person, with weekly totals in your own time zone. Weeks start on Monday unless you choose another day. A session that crosses midnight is split between the two days. When an Agent run works on an item whose board has a Time tracking column, its time is added by itself as an Agent session on the first such column. Runs shorter than a second, and refused or skipped runs, are not logged. A Time tracking column cannot be a form question, a formula input or a Lookup target, and it can only change into a Text column. The API is POST /v1/items/{id}/time with op set to start, stop, log, remove or estimate, and GET /v1/items/{id}/time for the totals. Agents use boardy_time_item and boardy_get_item_time. Source: worksong-ai/worksong:services/work/docs/dependencies.md@956ab3b, worksong-ai/worksong:services/work/docs/column-types.md@956ab3b, worksong-ai/worksong:services/work/docs/board-views.md@956ab3b. Docs version: Worksong 2.0 with Work 1.2.