| Table of Contents |
|---|
...
Tag Type –The broad category of what the tag is about or the purpose the tag serves.
E.g.: dissociate roles between “Agile” and “Traditional”, therefore creating a tag type as “Agile Role”.Tag Value –The label that fit under the broad category umbrella of the tag type.
E.g.: Product Owner, Scrum Master, Transformation Leads.
Each simple tag created is associated to a given type but represented as a single data point based on its value. For example, Product Owner, Scrum Master and Transformation Leads are 3 separate tag values within the Agile Role tag type, hence represented as 3 separate individual tags.
Tags with Attributes
Tag attributes need to be toggled on in the workspace setting.
| Info |
|---|
To understand how to enable and bulk import tags with attributes refer to Bulk import Tags with attributes (common attributes) For how-to guide on usage, refer to Import Tags with Unique Attributes |
What are Tag Attributes?
An single tag value can store additional data information often referred to as tag attributes.
Tag attributes can contain simple information like text, date, numbers or integers, or can reference an existing group (team), person or tag type –also known as ‘entities’.
For example, given a Cost Centre tag type, we can store the name of the different cost centres of the organisation as individual values. Say Cyber Security, IT Support and Marketing. Now for each of these individual cost centre, we are allowed to store additional information as attributes. For instance: the technical Cost Center ID used in the budgeting system, its Funding Source, the name of the department it is Owned By and the Time Frame it is set for.
...
Tag type: Cost Centre
Tag Value: Cyber Security
Tag Attribute - Cost Centre ID: 123456 [integer]
Tag Attribute - Funding Source: OPEX [text]
Tag Attribute - Owned By: CIO [person]
Tag Attribute - Time Frame: FY2025 [text]
Attributes can be entered in as a simple text information, or can reference other existing people or team information within TeamForm also known as ‘entities’.
There are 2 types of attributes within TeamForm and each have it’s unique behaviour to tags:
...
The two kinds of Tag Attributes
By default, all attribute values are common attributes. To add unique attributes to your tags, first toggle the feature on then add unique attributes to your tags.
Common attributes
Data stored as value with a common tag attribute will be applicable to all entities tagged with it. Hence changing the value of the attribute will update it for all groups, people or tag type associated with that tag attribute.
For example, people tagged as 2025 Graduate –a value for the Credential tag type– all share the same Completion Date as of March 31st 2024. If I update
...
this completion date to April 1st 2024,
...
all people
...
tagged as 2025 Graduate
...
will now have
...
display this updated completion date.
Unique attributes
...
It is possible to make the information contained as the value of a tag attribute unique to the entity it labels. Which means that changing the value of the tag attribute will not change for all
...
entities associated with it.
For example, two people can be tagged as
...
Departing but have unique
...
departure dates as attributes
...
. Changing the date for one won’t affect the date of the other.
Using attributes in the tag name
...
Attributes can be configured to be included in the tag name. Multiple attributes can be concatenated together with underscores to form longer dynamic tag names.
...
To understand how to enable and bulk import tags with attributes refer to Bulk import Tags with attributes (common attributes)
...
Reserved tags: Team Topology & Miro app
TeamForm supports using the lexicon from Team Topology team types and interaction modes to organise teams with tags.
These tags cannot be edited in the App UI and need to have their tags pre-populated via an integration.
If you are looking to recreate this behaviour you can use the pre-populated tagTypes and populate the tags in a similar way to the link above.
| Note |
|---|
These The two |
...
Users cannot search by a specific tag type in Planner or Forecast as search is only permitted at tag values level
You cannot download a list of tags based on an UI search, this needs to be done via backend back-end reports
Related information
...