Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Configuring a backlog and rank for existing epics

Updated on July 27, 2021

In Pega Agile Studio, epics belong to specific backlogs and can be ranked within the backlog. After an update, you must use the activity, PegaProjMgmt-Work.AssociateBLToEpic, to configure a backlog value on all non-resolved epics without backlogs in the system.

Pega Agile Studio Update Guide

To configure a backlog for existing epics, complete the following steps:

  1. Log on as an operator with access to Dev Studio.
  2. Open activity PegaProjMgmt-Work.AssociateBLToEpic.
  3. Click ActionsRun.
  4. On the execution modal, leave the default values unchanged, and then click Run.
    Verify the following steps:
    • On completion, the Operation completed screen is displayed if all existing epics are successfully associated with a backlog.
    • In cases where not all epics have been associated with a backlog successfully, a message in the format shown below will appear. In such cases, the system log will indicate which epics were not successfully initialized. These can be manually updated as needed.
    • For any epic for which a backlog could not be set, a message is displayed as shown when the epic is opened, and the user will need to set the backlog manually when it is next edited.
    • The report Epics Without Backlog, available in the Product Planning report category in the report browser, can be used to identify any epics that need a backlog assigned.
  • Previous topic Configuring the default backlog for existing products
  • Next topic Ranking epics in your backlog based on epic stories

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us