Finding things and answering questions
Tags
One word on a task or a project — #design, #retainer — and every list, board and report that can narrow to it, including each tag's hours against the rest.
A tag is a word your team chose, put on a task or a project so you can find everything that
carries it. #design, #waiting-on-client, #retainer. There is no set list and nothing to
design: if a word matters to your team, it is a tag. A value with a kind — an amount, a date, a
pick from a list — is a custom field instead, and whether work is billable is
its own switch, Billable, not a tag.
Tags are one of the switches in Team Settings → Features, and a new team starts with them off. An admin turns them on there.
Making tags
There is one list of tags for the whole team, under Team settings → Tags. Admins and members can add a tag there, rename it, and give it one of six colours. Only an admin can delete one, because deleting a tag takes it off every task and project that carries it.
You rarely need that page to start. Type #design when you
add a task and, if the team has no such tag, it is made on the spot and
put on the task. Tags match by name, not by case: #Design and #design are one tag.
Tags on tasks
On a task's page, the Tags row lists what the task carries. Pick one from Add a tag… to put it on; the × on a tag takes it off. Anyone who can edit the task can change its tags, and the change goes into the task's history.
Tags on projects
A project can carry tags of its own — #retainer on the projects you bill monthly,
#internal on the ones nobody bills.
- When you make the project, tick the tags on the New project form.
- Later, open the project, press Settings, and use the Tags row under the form. A tag goes on or comes off the moment you pick it; there is nothing to save.
Only admins change a project's tags, the same as the rest of its settings. Everyone who can see the project sees them: on its card on the Projects page and under its name on the project page. Press one to see every project that carries it.
A project's tags describe the project. They are not copied onto its tasks, and filtering tasks by a tag looks at the tasks' own tags.
Filtering by tag
Wherever work is listed, a Tag menu narrows it — and the address says tag=design, so a
filtered page is a link you can send.
| Where | What it keeps |
|---|---|
| Tasks | Tasks carrying the tag — see Finding things |
| Projects | Projects carrying the tag |
| The board and the calendar | The project's tasks carrying the tag |
| Hours logged | Hours logged on tasks carrying the tag |
| Workload | Open tasks carrying the tag, and the hours logged on them; every number opens the Tasks list with the same tag |
Put two names in the address with a comma — tag=design,launch — and you get what carries
either one. The menu only ever offers your own team's tags.
Hours by tag, against the rest
Hours logged has a By tag table once any task in the window carries a tag. Each tag gets a row with the hours logged on tasks carrying it, and Everything else beside it — so #design 32h, everything else 6h is one line. Hours on tasks with no tag at all are the No tag row. An hour on a task with two tags counts under both. The table is in the CSV too.
To see only one tag's hours, by person and by project, choose the tag in the Tag menu at the top, or press the tag in the By tag table. Billable hours against the rest have their own table, from the Billable switch rather than a tag — see Due dates, estimates, and logging time.
With tags switched off
Switching tags off takes away the menus and the Add a tag… pickers. It never takes a word
off anything: tags already on tasks and projects still show, a link that says tag=design
still filters, and turning the switch back on loses nothing.