Aha! Roadmaps | Use epics across releases and workspaces

Epics are used to group features that often share a common business objective. Although epics reside within the workspace and release where they will be completed, you can assign an epic to child features from multiple workspaces and releases.

If you want to standardize every epic that uses the same workflow, you can also create epic templates in Settings ⚙️ Account Statuses and workflows.

Click any of the following links to skip ahead:

• Use epics with multiple releases

• Use epics with multiple workspaces

Use epics with multiple releases

To use an epic to track a group of features that span multiple releases, here are a few options:

• If the delivery of your epic aligns with an existing release, place the epic in the release where you think it will be completed. Then, assign features to the epic. If the work is taking longer than expected, you can move the epic to the next release.

• If the delivery of your epic does not align with an existing release (or if you don't know when the epic will ship), create a new release that is dedicated to the epic. You can use the new epic to manage features that have been assigned to multiple releases.

In either case, use the Releases Gantt view to visualize your epic, including how your epic affects other releases and how you plan to deliver supporting features across several releases.

To increase the visibility of epics, you can customize your feature card and enable the Show epics setting to display epics and features together on the same board.

Top

Use epics with multiple workspaces

An epic can only live in one workspace, where it will be owned and tracked. However, you can link features from as many other workspaces and releases as you wish.

Top