| Table of Contents |
|---|
...
Tags can be used for teams to group teams by things they have in common (where this information is not already included in a work hierarchy), for example applications worked on, or team topology type (e.g. “Enabling Team”).
...
Other use cases of tags:
Skills repository - bringing skills in as tags against each individual
Funding information - bringing in cost centres, funding source categories and any other information in as tags that can be attached to people and/or teams
Resource Availability - to indicate who’s available by displaying who’s on what type of leave
...
There 2 fundamental elements that make up a ‘tag’ in TeamForm. They are: Tags can simply contain a type and a value:
Tag Type - This is the broad category of what the tag is about or the purpose the tag serves. eg: identify agile roles, therefore the tag type is then ‘Agile Role’
Tag Value - These are the values that fit under the broad category umbrella of the tag type. eg: Product Owner, Scrum Master, Transformation Leads
Simple tags are tag types that contain a single data point / tag value within each tag created. For example, Product Owner, Scrum Master and Transformation Leads are 3 separate tag values creating 3 separate individual tags within the same category of ‘Agile Role’ tag type.
...
...
Tags with Attributes
Within a single tag value we can store additional data information which is often referred to as ‘tag attributes’. For example within the ‘Cost Centre’ tag type, we have cost centre ID 123456 as the tag value and we now want to nest additional information such as CAPEX or OPEX associated to cost centre ID 123456.
...
There are 2 types of attributes within TeamForm and each have it’s unique behaviour to tags:
Common attributes - Data stored within the tag value is applicable to multiple teams or people, hence changing one value of the attribute within the tag value will change it for all teams and/or people with the same tag value. For example, two people are tagged as ‘2025 Graduate’ and have the same “completion date” as of March 31st 2024. If I update the completion date to April 1st 2024, both people with the 2025 Graduate tag will now have an updated completion date.
Unique attributes - Data stored within the same common tag value is unique to the team and/or person with the tag which means changing one value of the attribute within the tag will not change for all teams and/or people with the same tag value. For example, two people can be tagged as “Departing” but have unique “departure dates” as attributes, where departure date is an unique tag for the Departing tag.
Tags with attributes in the tag name: Attributes can be configured to be included in the tag name. Multiple attributes can be concatenated together to form longer dynamic tag names.
...
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 reports You cannot make
Related information
| Filter by label (Content by label) | |||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
FAQ
| Expand | ||
|---|---|---|
| ||
The name is what the user sees in the UI (ex. ‘Agile Role’), the ID is what is used for imports and Reporting (ex. ‘AGILE_ROLE’) |
...