Epic types

Epics can be workspace-specific or shared. Both epic types can exist in the Agile module only, or can be synchronized with the Strategy module.

Shared epics

You can create shared epics in workspaces that are members of the shared space. Shared epics are inherited by all the workspaces in the shared space.

Note: Creating or modifying shared epics requires space admin permissions. Other members of the shared space have read-only permissions.

The following table summarizes the characteristics of shared epics:

Feature	Details
Business rules	Only shared business rules apply to shared epics.
Fields	In shared epics, you can only define shared fields. Values set in the shared fields are reflected in all the workspaces. Note: In shared reference fields, such as Milestone, Release, and any shared user-defined fields, only shared items can be selected. The following fields are not available in shared epics: Owner, User tags, Waste, Waste category, Repeated phase, Requirements
Comments	Comments that are added to a shared epic in one of the workspaces are not available in the other workspaces.
Related items	A shared epic can have different related items in each workspace.
Convert	You cannot convert a shared epic to another entity type.
Follow	You cannot follow shared epics.
Bulk update	In a single bulk-update operation, you can only update epics that are either shared or isolated. You cannot bulk update epics of different types in the same operation.
Sequential ranking	Shared epics can only be ranked separately from isolated epics.
History	Changes to the shared epic fields are reflected in the epic's history.
Attachments	Attachments of shared epics are shared.

Local and synchronized epics

When you create an epic in the Agile module, you can define whether it is synchronized with the Strategy module, or exists in Agile only.

Use the Epic level field to define whether an epic is synchronized with the Strategy module.

Epic level value	Details
Undefined (default)	When you create an epic in the Agile module, the Epic level field is undefined by default, and the epic is synchronized with the Strategy module.
Local	This value prevents an epic from synchronizing with the Strategy module. Local epics exist in the Agile module only.
Portfolio	If an epic is created in the Strategy module, the Epic level field is automatically set to Portfolio, and the epic is synchronized with the Agile module. This value cannot be modified in the Agile module.

Tip: Add the Epic level column to the epics grid to understand which epics are synchronized with Strategy, and which exist in Agile only.

The admin can create business rules to define the Epic level field automatically. For details, see Set the Epic level field.

Epic products and portfolios

In the Strategy module, epics belong to a portfolio, a collection of solution sets that acts as a container for epics. In the Agile module, the backlog hierarchy does not include portfolios. Instead, the Product field in Agile reflects the epic's Strategy portfolio.

The values available for the Product field in Agile correspond to the portfolios defined in Strategy. If a portfolio is renamed or deleted in Strategy, the changes are reflected in Agile.

Note: In the Product field, a deleted portfolio is marked as deprecated for existing epics. For new epics, the deprecated value is not available. If the deleted portfolio has no active relations to other items, the corresponding value is no longer available in the Product field.

Depending on the epic level, use the Product field for the following purposes:

Epic level	Product field use
Epic synchronized with Strategy	The Product field identifies the portfolio that an epic is associated with in Strategy. When an epic is synchronized, its Product field is automatically populated with the value that corresponds to the portfolio associated with the epic in Strategy.
Local epic	While an epic is local, you can modify the Product value as needed. If you enable synchronization of an epic, you must assign the epic to a portfolio in Strategy. Then, the Product field is automatically updated with the corresponding value in Agile, and the field becomes read-only in Agile.

Epic level

Product field use

Epic synchronized with Strategy

The Product field identifies the portfolio that an epic is associated with in Strategy.

When an epic is synchronized, its Product field is automatically populated with the value that corresponds to the portfolio associated with the epic in Strategy.

Local epic

While an epic is local, you can modify the Product value as needed.

If you enable synchronization of an epic, you must assign the epic to a portfolio in Strategy. Then, the Product field is automatically updated with the corresponding value in Agile, and the field becomes read-only in Agile.

You can also use the Product field in dashboard widgets for analysis of both synchronized and local epics.

Tip: Space admins can modify the Product field name. This is useful, for example, if a user-defined field with the same name already exists in the space.

Features and backlog items

When features and backlog items are created, they inherit the Product value defined for their epic. If the Product value of an epic is modified, the change is not reflected in the epic's existing features or backlog items.

You can modify the Product value for features and backlog items, regardless of their epic's level.

Define epic business values

You can track the perceived and actual business values of epics. This helps you prioritize epics based on the value they deliver, and determine the gap between the initial and final estimation of an epic.

Epic value definition

An epic value is based on several factors, such as customer value, commercial value, market value, efficiency value, and future value.

The epic value definition depends on the methodology adopted by the product team, and may vary across teams.

You can define an epic value in two stages:

Value	Description
Perceived value	The epic's initial value estimation that helps prioritize the epic relative to others. The perceived value is estimated by the product team when creating an epic and determining its business priority. Tip: The perceived value score should justify an epic's priority over other epics.
Actual value	The epic's true value, as concluded after the implementation and delivery of the epic. The actual value score is calculated by the product team to track the value gap for different epics over time. Note: Define the actual value in the epic details after the epic’s implementation.

Value

Description

Perceived value

The epic's initial value estimation that helps prioritize the epic relative to others.

The perceived value is estimated by the product team when creating an epic and determining its business priority.

Tip: The perceived value score should justify an epic's priority over other epics.

Actual value

The epic's true value, as concluded after the implementation and delivery of the epic.

The actual value score is calculated by the product team to track the value gap for different epics over time.

Note: Define the actual value in the epic details after the epic’s implementation.

After the epic actual value is defined, the value gap is automatically calculated. The value gap is the difference between the perceived and actual values of an epic.

Note:

You can edit the perceived and actual value scores in any phase of an epic. The value gap is automatically recalculated.
You can use decimal numbers for value scores.
Your admin can set the minimum and maximum value scores with the help of a business rule. For example: The perceived value field should be between 1 and 100. For details, see Design business rules.