Labels, milestones & dates

Labels

Labels are coloured tags for slicing work - bug, design, Q3. A task can carry several, and any view can be filtered by them.

Dates

A task can have a start date, a due date, or both. A Noot itself has a start date and a target date, shown in its header as a schedule strip - "Starts" flips to "Started" once the date passes, next to the target and the next milestone.

Milestones

Milestones mark the moments that matter - a beta cut, a launch, the end of a phase. There are two kinds, and both are real:

• Noot milestones - set at creation under Dates & milestones, or later. They drive the header's next-milestone chip, the diamonds on the Timeline and Gantt milestone rails, and the calendar.
• Task milestones - added from the task detail. They show as pips on the task's own timeline bar and as chips on its card; overdue ones turn coral, done ones grey out.

Organization milestones

Somebody who can manage the organization can set a milestone for every project at once under Organization → Milestones - a quarter close, a launch, an audit. Press Add milestone, give it a name and a date (and a description if it helps), and it lands on every project in the workspace, private ones included, and on every project created afterwards. It is a real project milestone on each one: it shows on the Timeline and Gantt rails, on the calendar and in the project's Overview, cards can be due at it, and Noots asks whether it was achieved when the date arrives.

• Sub-organizations - if the workspace has sub-organizations, the dialog offers Also add to sub-organizations and their projects. It is off unless you turn it on. With it on, the milestone lands on every project in every sub-organization too, and people there see it as set by your workspace, under From and your workspace's name on their own Organization → Milestones.
• Read-only in a project - its name and date belong to the organization, so a project cannot rename, move or remove it; it says Set by and the organization's name wherever it is drawn. Whether that project achieved it is the project's own to mark.
• Editing and removing - change the name or date on Organization → Milestones and every project follows (cards due at it move with it). Removing it asks first, with the number of projects it will come off.
• One question, not one per project - when the date arrives, somebody who is asked about it for several of their projects is asked once, and a yes marks it achieved on each of them. A no leaves the date where it is, because the organization sets it.
• From inside a project - adding a milestone from a project's Timeline (+ Milestone) or its milestones panel offers Add to every project in your organization, if you can manage the organization and it has more than one project (and and its sub-organizations when it has any). Ticked, it becomes an organization milestone instead of that project's own, and each project shows it as Set by your organization. Every one of those editors links to Manage organization milestones.
• Ask Hoot - "add a Market validation milestone across all projects on 20 November" makes Hoot prepare ONE organization milestone card; nothing is set until you press it. Hoot never turns a milestone into tasks. A milestone on one named project stays that project's own. If you cannot manage the organization, Hoot offers a milestone on one project instead.