Creating, renaming, and deleting tags for global configurations and components
Tags are strings without spaces or commas and are project-area
specific.
Define tags so that team members easily find and organize global configurations and components in
the Global Configuration Management application. Delete and rename tags as needed by your
project.
Before you begin
You must be assigned the Tag Manager role or have the permission in the Tags permission group to create, delete, or rename tags.
About this task
- Tags are strings without spaces or commas and are project-area specific. You can nest tags to
represent a hierarchy, such as
country/state/city
. The forward slash (/) separates tag levels: - When you delete a tag, it and any nested tags are deleted and you can no longer use them. You
can re-create a deleted tag again if you need it.
Continuing with the example:
On the Browse Components and Browse Configurations pages, in the Tags section, when you delete the
state
tag, thecountry/state
andcountry/state/city
tags are removed from items and deleted. You can still use thecountry
tag. - Tags do not span project areas. Queries for tags show only the configurations from the same project area as the query. If a configuration lead defines the same tag in multiple project areas and you must rename or delete a tag to suit your project needs, you must query configurations in each project area for the tag.
-
Important: Avoid adding classified or sensitive data such as customer names and proprietary information to tags. If you must scrub the Global Configuration Management data later, tags are removed from the artifacts you scrub, but the tags are not permanently deleted from the repository. See Deleting sensitive data.
- Tags do not organize components or configurations into a physical hierarchy; they simply help you to view them in logical groups.