...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
| Table of Contents |
|---|
What are tags?
In general tags are a way to categorise people and teams. They are highly customisable and can include things like could relate to many things such as skills, cost centre, funding source, leave type, etc.
Tags provide a visual flag and a way of discovering groups of people or teams “tagged” i.e. within a category. Against the person or team they can have
People and teams can be linked with multiple different tags against themwithout limitation.
There are also advance advanced use cases of tags that is allowed in TeamForm where it tags can be used to specify requirements during workforce planning, or be linked to comments and specification of membershipsother elements such as comments or membership specifications.
What are common use cases for tags?
Linking people with tags
Tags can be used for people to highlight their agile “hatted role” for example, a an “Agile Coach” tag. This is useful because an agile hatted role may be different from an individual’s official role or job title. Defining a list of “Specialist” tags allows or tags to capture these “Specialities” can allow an organisation to easily label these individuals so they can be found through search, or by visually identifying through use of a “badge” (see below).
...
Linking teams with tags
Tags can also be used for teams (also referred to as groups)to group teams by things they have in common (where this information is them by a commonality not already included in a their work hierarchy), for example applications worked on, or team topology type . For example to highlight common tools or 3rd party applications they use to do their work, or their type in a given lexicon (e.g. “Enabling Team” in the lexicon from Team Topologies).
...
Other use cases
...
for tags
Advanced applications for Tags can be used in many more contexts, such as
Skills repository - bringing –bringing skills in as tags against each individual. See What are skills?
Funding information - bringing –bringing in cost centres, funding source categories and any other information in as tags that so they can be attached to people and/or teams.
Resource Availability - to –to indicate who’s available by displaying who’s on what type of leave.
For details on when tags should or shouldn’t be used, refer to When to use Tag vs People Attributes
What are the 3 different kinds of tags?
Simple Tags
There The 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 –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
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. eg
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 / tag value within each tag createdbased on its value. For example, Product Owner, Scrum Master and Transformation Leads are 3 separate tag values creating within the Agile Role tag type, hence represented as 3 separate individual tags within the same category of ‘Agile Role’ tag type.
...
For how to guides on how to configure or bulk import simple tags, refer to /wiki/spaces/OR/pages/2569043969
Tags with Attributes
...
Tags with Attributes
Tag attributes need to be toggled on in the workspace setting.
What are Tag Attributes?
An single tag value 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.
...
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:
...
tag attributes.
Tag attributes can contain simple information like:
Text;
Date;
Numbers; or
Integers.
They can also reference:
Existing groups (team);
Person; or
Tag type.
These later are 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.
So for an individual tag associated to a specific value for this type:
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]
...
The two kinds of Tag Attributes
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.
To understand how to enable and bulk import tags with attributes refer to https://teamform.atlassian.net/wiki/pages/createpage.action?spaceKey=OS&title=Import%20Tags%20with%20attributes%20%28common%20attributes%29.
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.
See also more information on how to Import Tags with Unique Attributes.
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
...
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 two |
| Info |
|---|
See this article for more information on how this works How to use the Miro Team Topologies plug-in |
What attributes can be sourced from TeamForm?
Existing TeamForm information can be stored as attributes within tags. This includes:
Specific person that exists in TeamForm
Specific Tag Type
Teams that exists in TeamForm
Other manual attributes that are allowed in tag types are:
Text
Date
Number and Integers
Where can tag information come from?
2 main sources that can coexist:
Tags are data stored in TeamForm (manual entry, bulk import, etc) → TeamForm is the source of truth for this information
Tags are source come from somewhere else (ex: a Skills systems, HRIS, Portfolio Management) → TeamForm shows the information and we recommend that users don’t edit it in TeamForm
...
be imported via integration.
Which source of truth for tags?
Tags can coexist between TeamForm and other Enterprise HRIS. This leads to two scenarios:
An HRIS other than TeamForm is source of truth –Tags are sourced from a Skills System, Portfolio Management tool or else and kept up to date in TeamForm through regular imports. In which case we recommend that users don’t edit the tags in TeamForm are those changes would be erased by subsequent imports.
TeamForm is source of truth –Tags are created and/or subsequently updated and maintained in TeamForm. Upon import, TeamForm information prevail.
Limitations in tags usage
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 A list of tags based on an UI search, this needs to be done via backend reports
You cannot make
search in the UI can't be downloaded. Extraction can however be done through back-end reporting.
Related information
| Filter by label (Content by label) | |||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Child pages (Children Display) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
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’) |
...