Epic types

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

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.

In shared epics, you can only define shared fields. Such field types include: boolean, time, string, memo, and other non-calculated fields.

Values set in the above fields are reflected in all the workspaces.


  • In shared reference fields, such as Milestone, Release, and any shared user-defined fields, only shared items are available.
  • 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.


Not available


Not available

Integration with Microsoft Teams

Not available

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 a single operation.
Sequential ranking Shared epics can only be ranked separately from isolated epics.

Changes to the shared epic fields are reflected in the epic's history.

Attachments Attachments of shared epics are shared.

Back to top

Local and portfolio epics

By default, all epics that you create in ValueEdge Agile are automatically synchronized with ValueEdge Strategy. You can define that an epic should not be synchronized with ValueEdge Strategy, and should exist in ValueEdge Agile only.

Use the following fields to control an epic's behavior:

Field Details
Epic level

By default, the Epic level field is undefined. Depending on whether an epic was created in ValueEdge Agile or ValueEdge Strategy, the epic level can be set to Local or Portfolio.

  • Epics created in ValueEdge Agile: Use the Epic level field to define whether an epic should be synchronized with ValueEdge Strategy, or whether it should exist in ValueEdge Agile only.

    Consider the following Epic level options:

    • Undefined (default): An epic is automatically synchronized with ValueEdge Strategy. To stop synchronizing the epic, set the field to Local.
    • Local: This value prevents an epic from synchronizing with ValueEdge Strategy. Local epics exist in ValueEdge Agile only.

      To start synchronizing a local epic, clear the Local value and save the change.

  • Epics created in ValueEdge Strategy: The Epic level field is set to Portfolio by default, and cannot be modified in ValueEdge Agile. This means that you cannot stop the synchronization of such epics in ValueEdge Agile.

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

You can create business rules to define the Epic level field automatically. For details, see Rule examples.


Epics in ValueEdge Strategy belong to a portfolio, a collection of solution sets that acts as a container for epics.

In ValueEdge Agile, the backlog hierarchy does not include portfolios. You can use the Product field to associate epics with their respective portfolios in ValueEdge Strategy.

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

  • Portfolio epics / Epics with the undefined level: To identify the portfolio that an epic is associated with in ValueEdge Strategy.

    Since these epics are synchronized with ValueEdge Strategy, their Product field is automatically populated with the value that corresponds to the portfolio an epic is associated with in ValueEdge Strategy.

  • Local epics: To associate an epic with a portfolio in ValueEdge Strategy.

    While an epic is local, the Product value has no effect, and you can modify it at any stage.

    If the Field level Local value is cleared, and the synchronization is enabled, the Product field is automatically updated with the respective portfolio in ValueEdge Strategy. The field becomes read-only in ValueEdge Agile.

    Note: The Product field is not populated immediately after the synchronization is enabled. First, a new epic in ValueEdge Strategy needs to be assigned to a portfolio. Then, the updates are synchronized and reflected in ValueEdge Agile.

You can also use the Product field in dashboard widgets for analysis.


  • The values available for the Product field in ValueEdge Agile correspond to the portfolios defined in ValueEdge Strategy. If a portfolio is renamed or deleted in ValueEdge Strategy, the changes are reflected in ValueEdge Agile.
  • In the Product menu, 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 portfolio is no longer available in the Product dialog box.

  • An epic's features and backlog items inherit the Product value defined for their epic. You can modify the Product field for features and backlog items, regardless of their epic's level. You cannot change the product for an epic that is being synchronized.

    If the Product field of an epic is modified, the changes are not reflected in the epic's features or backlog items.

  • Space admins can modify the Product field name. It can be useful if, for example, a user-defined field with the same name already exists in the space.

Back to top

See also: