Labels Overview

In the Portfolio Management application, a Label serves as a tag that you can apply on any record to attach categorical information, such as topic, priority, development task and much more to them. 

Labelling the records allows ordering, filtering or grouping the records based on different properties. The records that share the same label get logically linked to each other. Thus, categorization or grouping becomes easy.  

A single record can have more than one label applied. As a result, the record could appear in different label searches alongside various groups of records.

For example, a task, DemoTask1, is tagged with labels: Label1, Label2, and Label3. On searching for Label1, DemoTask1 will appear in the search results with all the records labelled as Label1. Similarly, on searching for Label2 and Label3, DemoTask1 will appear alongside other records, labelled Label2 and Label3, respectively. These distinct groups of records accompanying DemoTask1 in these searches may vary from each other.

The labels can be applied to any record irrespective of the root object type, following some conditions, which we will discuss in the later sections. However, creating a Label is only possible on the Application, Portfolio, Program, and Project levels. 

Types of Labels

The labels are categorized based on the following types:

Pre-Configured Labels

Pre-Configured Labels are the one that comes available in your application. Further creation of new Pre-configured Labels is taken care by the administrator of the application.

Pre-Configured Labels are created on the Application level and thus can be applied to any record present in the application.

How to create a Pre-Configured Label?

Only the application admins have the authority to create Pre-Configured Labels.

For more information, see Creating-and-editing-Pre-Configured-Labels.

Custom Labels

Custom Labels are the ones an end user creates on Portfolio, Program, and Project levels. Creation of these custom labels is generally taken care by the respective Portfolio, Program and Project Managers or by the Admin.

• An Admin can create a Custom Label on any or all the underlying Portfolios, Programs, and Projects.
• The Portfolio Managers can create Custom Labels within their Portfolio as well as within all the underlying Programs and Projects.
• Similarly, the respective Program Managers can create Custom Labels within their Program and all the underlying Projects.
• The Project Managers can only create the labels only within their Project.

How to create a Custom Label?

The application Administrators, Portfolio Managers, Program Managers and Project Managers can create custom labels. 

For more information, see Managing-Labels. 

Primary Label

A Primary Label describes only the most important piece of information.

The selection dropdown of a Primary Label field contains all the labels created within the Portfolio, Program, and/or Project up in the hierarchy.

For example, suppose a Project Task, Task1 is created within the Project, Project1, which is under Program1, and all these belong to a Portfolio named Portfolio1. If we go to apply a label on this Project Task, Task1, the selection dropdown of its Primary Label field will contain all the labels created within Portfolio1, Program1, and Project1. If there is no Program (Project1 is directly under Portfolio1), the selection dropdown will only show the labels created under Portfolio1 and Project1.

You can select only one out of the available Labels as Primary, depending on the requirement.

Secondary Labels

Secondary labels are the ones that provide you with more details about the record they are applied on. The selection dropdown of a Secondary Label field contains all the labels created within the Portfolio, Program, and/or Project up in the hierarchy, except the one we choose as the Primary Label. Unlike Primary labels, you can select multiple labels as Secondary, depending on the record.

Related topics

Creating Custom Labels

Applying-Labels

Creating and editing Pre-Configured Labels