Epic transfer

Within the Product:

When transferring an Epic to a Capability within the same Product, located in any Subsystem, there are no restrictions. If the Epic is decomposed and tasks are at the WF stages:

• To Do: There may be a change in the priority of their execution, depending on the change in the business weight of the Capability and/or Subsystem to which the Epic has been moved. Assignments for performers who have not yet started working may be canceled, and performers may receive other tasks.
• Doing, Review: The priority of their execution remains the same; no changes occur. If a task is returned from the Review stage to the To Do stage, the priority of execution may change, depending on the change in the business weight of the Capability to which the Epic has been moved.
• Done: Changing priorities does not affect them; they move like all other decomposition elements without changes in data and relationships.

Transferring an Epic to a Capability in another Product:

• If the Epic is not decomposed and has no link to the increment, there are no restrictions.
• If the Epic is linked to the increment in any status (is defined / not defined), notify the user and break the link.
• If the Epic is linked to the increment in the status is defined and is decomposed into tasks:
  • The user receives a warning about breaking the link and removing tasks from the WF stages.
  • Upon confirmation, the link with the increment is severed, tasks are removed from the stages.
  • All decomposition elements retain their data and properties according to the rules of breaking the link between the Epic and the increment.