Map Demand to multiple EPICs

[Shantharao]

Hi All,
in the OOB we can create one Epic from Demand,
But there is a business use case stating single Demand can be mapped to multiple Epics, 
Do we have any alternate solutions without impacting the OOB business logic?

Thanks in advance for your help and suggestions, have a nice day.

[Bert_c1]

Hi Shantharao,

OOB The 'rm_epic' table does have a field named 'demand' that is a reference to a record in the 'dmn_demand' table. So you should be able to have multiple records in 'rm_epic' that refer to a single record in the 'dmn_demand' table. However, I see as admin I can not set values for the 'demand' field on 'rm_epic'. So that needs to change to do what you want. The 'Read-only' field is set on the dictionary record, clearing that allows adding values in the field. But then that is a change to OOB configuration.

Maybe others here familiar with Agile Development in Servicenow can advise you.

[Dominik Simunek]

Hi Shantharao,

A possible option which is "baseline" is to create one Epic and then create child Epics in it. Since Epics allow to have parent-child relationship, you can easily achieve having multiple Epics out of a Demand. But it will be like:

- Demand -> Epic "A"

- Epic "A" -> Epic "B", Epic "C", Epic "D"...

Best regards,

Dominik