Skip to content

Docs

Project management

Tasks for client and internal work in one place, with four ways to look at them: the day in front of you, the week you are planning, a flat table, and a board per project.

Where to find it: Project Management in the mode switcher. It lands on My Day.

What this section is about

A task belongs to a project and is the unit everything else attaches to: time is logged against it, comments and files hang off it, and a Jira issue can mirror it. Anybody on the team can create one.

The four views are not four features — they are one set of tickets read four ways. My Day is what is in front of you right now. My Week is where the coming days are already full and where there is still room. Table is a flat list you can filter. Board is one project's columns.

Due dates are the only scheduling mechanism, deliberately. Putting something on today, moving it to Thursday, pushing it a week and taking it off this week are all one act: changing the date. There is no second, private notion of "this week" that could disagree with the date everybody else sees.

Important features to use

  1. 01My Day is the landing view, and it is a short list on purposeAssigned to you and due today or earlier. A finished ticket due today stays, because it is the day's progress; a finished overdue one drops out, because it is history. You can page back to check a day over, and anything you log while looking at an earlier day is dated to that day.
  2. 02My Week has three tabs because a week has three questionsPlan arranges the days, Check in measures against pace mid-week, Review tallies what you said against what you did. It opens on the tab the day calls for — Monday on Plan, mid-week on Check in, Friday on Review — and each day column has its own + for adding work to that day.
  3. 03Board columns are per project and are an admin's to setA new project gets To Do / In Progress / Blocked / Done. Admins rename, recolour, reorder and add columns on the project's Board columns editor. Every column carries a category — to do, in progress, done — and that category is what carries the meaning, so a column called "Shipped" still counts as done everywhere.
  4. 04Tags are each client's own vocabularyType a word into the Tags field on a ticket and it exists for that client from then on, available on all their other tickets and in the filter. They are per client rather than per project, so the same word means one thing across a client's whole account, and anybody on the team can create one.
  5. 05A ticket can have several assignees, with one leadEveryone assigned can log time against it; the lead is who owns it. Logging time requires being assigned — if the ticket has nobody on it, logging time assigns you automatically. Taking somebody off a ticket detaches the time they logged on it.
  6. 06Dragging a card writes the whole columnA drop renumbers every card in the columns it touched, in one go, so the order you see is the order that is stored. Drag is withheld while a filter is on — reordering a list you can only partly see would stamp positions over the cards you cannot.
  7. 07Copy link on a ticket gives a URL that opens itIt works from anywhere — a Slack message, a notification, an email — and opens the ticket in a dialog even if it is not in the list you happen to be looking at.
  8. 08The review queue is for tickets an agent was unsure aboutRiley creates tickets from recorded meetings and flags the ones where it could not tell which project they belong to, rather than discarding them. They are real tickets on real boards; the queue is where you correct the filing.

Common questions

A new card appears at the top of the column. Is that configurable?
No, and it is deliberate: the + that creates a card is in the column header, so a card appearing at the foot of a thirty-card column reads as not having been created. Tickets an agent files from a meeting are appended to the bottom instead — an arrival nobody asked for belongs out of the way.
I dragged a card and it snapped back. What happened?
That was a real bug and is fixed. If you see it again, check whether a filter is on — the board withholds dragging while filtered, because the order it would write covers cards that are hidden.
Can I move a ticket to another project?
Yes, within the same client. The board column is re-resolved for you (columns are per project). Across clients is refused — that is far more often a mistake than an intent.
Why can't I log time against this ticket?
You need to be one of its assignees. If nobody is assigned, logging time assigns you; if somebody else is, add yourself or ask the lead to.
What does the estimate field do?
It is displayed, and that is all. Nothing in OS3 plans or forecasts from estimates, because almost no ticket carries one — My Week's pace line counts tickets against days elapsed rather than pretending to weigh them.
Can I un-complete a ticket from My Day or My Week?
Not with the tick — completing moves a ticket to the project's first done column, and the reverse has no single answer, since OS3 cannot know which column it came from. Reopen it by changing its status in the ticket itself.