Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
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.

image-20240229-111412.png

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.

...

Tag attributes can contain simple information like text, date, numbers or integers, or can reference an existing group (team), person or tag type –also :

  • 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.

...

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 Bulk import Tags with attributes (common 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.

...

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

...

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 search in the UI can't be downloaded. Extraction can however be done through back-end reports reporting.

Related information

Filter by label (Content by label)
showLabelsfalse
max5
spacescom.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@9e4
maxCheckboxfalse
showSpacefalse
sortmodified
typepage
reversetrue
labelsteam team-details types
cqllabel in ( "system-admin" , "tags" , "tagtypes" , "power-user" ) and type = "page" and space = "OS"

...