Tag work with shared labels

Project structure groups work by where it lives, a task lives in one project, under one epic, in one sprint. Tags group it by what it is, across those boundaries: every “tech-debt” task across twelve projects, every “compliance” item across three years, every “customer-blocker” no matter who owns it. The discipline that makes tags valuable: keep the pool small (a handful of tags the team can hold in working memory), keep names short (one word beats four), and agree on what each one means before everyone starts inventing them.

How tags work

• Organization-wide: tags are defined once and usable on tasks in every project. There are no per-project tag lists to keep in sync.
• Color-coded: each tag carries a color, and tagged tasks show the tag as a colored pill directly on the task row, so a scan of the list picks them out immediately.
• Short by design: tag names are capped at 30 characters. A tag is a label, not a sentence.

Tag a task

1. Open the task and find the tags control.

2. Pick any existing tag to apply it. To remove an applied tag, select the small x on its pill.

3. Need a new one? Type the name right there, pick a color, and create it without leaving the task. The tag is immediately available to everyone in the organization.

Who can manage tags

By default, every organization member can create and manage tags; guests cannot. Organizations that want a curated taxonomy can restrict tag management to specific roles through the permissions matrix in Organization Settings.

Tip

Agree on a handful of tags before the team starts inventing them. Because the pool is shared, “bug”, “bugs”, and “defect” will otherwise coexist within a week, and a label that means three things means nothing.

Tags and automation

Workflow automations include Add tag and Remove tag actions, so labeling does not have to be manual. A workflow that tags every task created from a particular trigger gives you a permanent marker for where work originated.

Best practices

1. Keep the tag pool small, under twenty active tags. A taxonomy of six tags everyone uses correctly beats a taxonomy of forty where half are misspellings of each other. When the list grows past twenty, prune the redundancies before adding the next one.
2. Establish naming conventions early. Decide on singular vs plural (“bug” not “bugs”), language (“issue” vs “defect” vs “ticket”, pick one), and avoid spaces inside tag names where possible. The convention only matters if everyone follows it, so publish it in your team’s documentation and link from the organization’s onboarding.
3. Use color to encode urgency or domain, not random assignment. Red tags for blockers, yellow for risk, green for cleanup, blue for customer-impact, gray for neutral. The colors carry meaning at a glance; “what color of tag this is” becomes a fast scan signal.
4. Use tags + automations to enforce labeling. A workflow that auto-tags every task created from an intake form, every task moved to Blocked, or every task linked to a particular goal gives the team a permanent marker without anyone having to remember to add it. See Build a workflow.
5. Prefer tags for fluid categorization, custom fields for structured data. “Customer-impact” is a tag (qualitative shorthand); “Customer ID” is a custom field (structured value the team will report on). Reach for tags first; if the data needs filtering, sorting, or appearing in reports as its own column, promote it to a custom field.

Troubleshooting / common pitfalls

• My new tag isn’t appearing for others. Tags are org-wide, so a tag you create is immediately visible to everyone. If a colleague says “I don’t see your tag,” they may be looking at a cached page, refresh. If you genuinely can’t see each other’s tags, you might be in different organizations (organization switcher).
• The tag I want already exists with a slightly different spelling. Don’t add a new variant; pick the existing one and update your tasks to match. If the existing tag really is wrong (typo), rename it for the organization rather than adding a parallel.
• The tag dropdown is overwhelming. That’s the symptom of an over-grown tag pool. Audit the list, merge similar tags via bulk-retag, and delete the dead ones. The pool should fit on one screen.
• I tagged a task but the visible pill is missing. Two causes: (a) you’re looking at a view that doesn’t render tags; pills appear on rows in the List view, while Kanban cards, Gantt bars, and Grid rows don’t show them (open the task to see its tags there); (b) the tag was deleted by someone with admin permissions after you applied it. Re-add the tag.
• I can’t remove a tag from the pool. Tags carrying values on real tasks can’t be deleted directly without removing them from every task first. Either bulk-retag the tasks via the list view, then delete; or rename the tag to “[Deprecated] X” so it’s clearly out-of-bounds for new use.

How this combines with other features

• Tags + Automations. Workflow automations can add or remove tags as steps. A workflow that auto-tags every task from a particular intake form with “external- request” gives the team a permanent marker for where work came from. See Build a workflow.
• Tags + Reports. Cross-project Reports group tasks by status, owner, portfolio, month, or score, not by tag. Tags do show up as a column in a project’s Excel export, so once you’ve exported you can filter or pivot on them there. See Run cross-project reports.
• Tags + Custom Dashboards. Dashboard widgets don’t have a tag filter either. Tags stay a visual, scan-while-you- look layer rather than a reporting dimension on any surface today. See Build a custom dashboard.
• Tags + AI assistant. Ask “summarize tasks tagged ‘tech-debt’ across my projects” or “what’s blocked and tagged customer-impact?”, the assistant reads tags as first-class filters. See Chat with Onplana AI.

Coming from another tool

Tool	Mapping
Asana tags	Direct concept; same shared-across-org model
Jira labels	Jira labels ≈ tags; Onplana adds color-coding by default
Trello labels	Direct concept; Onplana’s are org-wide rather than per-board
Linear labels	Direct mapping; Linear has team-scoped labels, Onplana’s are org-wide
GitHub labels	GitHub’s are per-repo; Onplana’s span every project (analogous to org-level labels)

FAQs

Can I filter a view by tag? The task views do not have a dedicated tag filter today. Tags work as a visual layer: the colored pills on each row make tagged work easy to spot while you scan, search, and filter by the other fields.

What is the difference between a tag and a custom field? A dropdown custom field is structured data: one defined place on the form with controlled values. Tags are freer: any number per task, created on the fly, shared everywhere. Use a custom field when reporting depends on it, tags when the team just needs a shared shorthand.

Do tags work on projects too? Tags are applied to tasks in the app today. Projects are better distinguished by their built-in fields: status, type, and the billable flag, all of which the Projects page can filter on.

Is there a limit on tags per task? Practical limit is high (you can stack many tags on a single task), but the list row wraps the pills onto extra lines past a few. If you find yourself applying more than 5-6 tags to a single task, the structure is too free-form, consider whether one of the tags should be a custom field or a different epic.

Can I import tags from another tool? There’s no dedicated tag import flow today. The cleanest pattern: on your first .mpp import or large project creation, add the tags you need in the same session and bulk-apply them via the list view.

How do tags interact with Guests? Guests can see tags on tasks they’re shown (which carry the colored pill), but cannot create new ones or change the tag pool. They can remove a tag from a task they edit if they have edit permissions.

Will my tags survive a project delete and restore? Yes. The recycle bin’s project-restore snapshot includes tag associations on every task, so restored tasks come back with their tags intact. See Restore deleted work from the Recycle Bin.

Related

• Create custom fields, when tags aren’t structured enough
• Build a workflow, auto-tag tasks at create/move
• Run cross-project reports, why tags are not a reporting dimension and what to use instead