How to bring your Epics in EAP into your CWM Boards using Connected Work
Workaround guide for teams that create and manage epics in EAP and want to bring them to CWM Boards
Temporary fix
This is a temporary workaround, not a permanent setup. We plan to improve this in CWM Lux experience, where these steps will be automated, so you will not need to build the integration by hand.
Who this is for
This guide is for teams that have created and managed their epics as scrum epics (sn_align_core_scrum_epic) in EAP and they want to bring those epics into their CWM Boards
The steps below show ways to integrate rm_epic and sn_align_core_scrum_epic with a two-way sync between them. Once integration is in place, you can bring shadow epics from rm_epic into CWM with Connected Work using same filter conditions, and changes you make to an epic in rm_epic are reflected back in the scrum epic.
The tables involved
| Table | What it is |
|---|---|
| rm_epic | Legacy epic table used mainly in Agile Development 2.0 |
| sn_align_core_scrum_epic | Scrum epic table used in EAP, shared between EAP and CWM |
A story to start: where your epics live
Picture a team that plans its work across two products. The first product is Enterprise Agile Planning (EAP) where leadership works at the planning levels, such as portfolios and solution trains, and it is where epics are planned and created. Each epic created in EAP is added in the scrum epic table (sn_align_core_scrum_epic). Unfortunately scrum epic table is not a task table and hence these epics cannot be brought to the CWM Boards directly using Connected Work
The second product is Collaborative Work Management (CWM), where teams do their day-to-day work. CWM is built for teams to manage every day work, such as stories and tasks, and it gives each team the freedom to decide how that work is organised and displayed. Teams that run Scrum on Agile Development 2.0 used the older rm_epic table as their epic table. Since rm_epic table is a task table, connected work feature can be used to bring them to the CWM board.
Riverside is one of these teams. Its epics were planned in EAP (sn_align_core_scrum_epic table), not in the Agile 2.0 product (rm_epic table). So when Riverside wants its epics on its CWM board, cannot bring those scrum epics into CWM directly through Connected Work.
Instead, it’s ServiceNow admin sets up a backend integration that builds a bridge between the two epic tables. The steps below show how to set it up, so that epics planned in EAP can reach the rm_epic table and from there appear on your CWM board. The steps in this article connect all of it.
Setup steps
- Install Agile Development 2.0, Strategic Planning Advanced, and CWM.
- SPW installs the integrations.
- In the All navigator, search for SPM integrations.
- Go to Integrations.
- If no internal integration exists, click New.
- Click Create ServiceNow Internal integration.
- Open the newly created configuration using the info icon.
- [Caution - This will override all existing mappings for all other integration - Check Step 10] Click Generate Default Mapping Configuration.
- This generates the mapping for Project, Demand, Milestone, Feedback, and Epic.
- Do not run step 9 if a configuration already exists. Step 9 can overwrite existing configurations. Refer to the documentation on how to create the integration specific for Epics instead.
- Use Connected Work to bring epics from rm_epic. Any change made in rm_epic is reflected in sn_align_core_scrum_epic.
Check before step 9
Generating the default mapping can overwrite an existing configuration. Confirm that no integration configuration is already in use before you generate it.
