Data Model

Tags

Create the tags people can put on items, group them into collections, and decide which item types can carry which tags.

Tags are the lightweight, cross-cutting labels on an item: Backend, Design, Research, Roadmap Item. Unlike item types (one per item, hierarchical) and statuses (one per item, workflow), an item can carry any number of tags, and you can filter, group and automate on them. Use tags for anything that cuts across your hierarchy.

Where to find it

Configure Settings → Data Model → Tags. The page needs the Manage labels permission (default Owner and Admin roles). It has the three columns shared by all Data Model pages: create the things, group them into collections, assign collections to item types.

1 - Create Tags

Click New and fill in Tag Name, an optional Tag Description, and a Tag Color. Names are unique within the organization.

Two tags are Reserved by System and cannot be renamed or deleted:

  • Bug — marks an item as a defect; DevStride uses it in reports and filters.
  • Blocked — marks an item as blocked; boards and the Gantt call it out.

Everything else is User Defined. Edit a tag with its pencil, or delete it with the red X; deleting removes it from every item that carried it.

2 - Group into Collections

Click New to create a Tag Collection, then drag tags from the pool into it; drag within the collection to order them and drag out to remove. Removing a tag from a collection does not delete the tag. A new organization has one collection, Default, containing the system tags. In a long list, hold the item on the band at the top or bottom edge and the list scrolls straight away.

3 - Assign to Item Types

For each item type, choose the collection whose tags it may carry. An item only offers the tags in its type's collection, so a Marketing Task can have a different tag set from a Story. Changing a type's collection needs the Manage work types permission as well.

When you switch a type to a different collection, tags that are not in the new collection are removed from existing items of that type; tags it shares stay. This happens quietly in the background: the change is recorded in each item's history, but nobody is notified and no automation runs.