Story Scoping Limitation in DPR Releases

[varshacpra]

Hi  All,

We would like to raise a concern regarding Epic and Story scoping in DPR.

Epics typically span up to 3 months, while Stories represent shorter delivery cycles. In practice, not all Stories from an Epic are delivered in the same release , some may go into one release, others into a different one.

When a Product Enhancement (created from an Epic) is associated to a release, all its Stories are automatically scoped. There is no option to split Stories from one Epic across multiple releases.

This forces an all-or-nothing approach at the Epic level, which does not reflect how teams actually plan their deliverables.

Is it possible to create Product Enhancements from Stories instead of Epics, to allow better scoping at the Story level?

We would appreciate if a workaround is available for this

[Siva Sankar Ala]

If your epics are spanning more than one release, we'd recommend modeling them as features instead. Digital Product Release has a dedicated Product Feature record type designed exactly for this: a Product Feature represents work that spans multiple releases, while an Epic represents the slice of that work scoped to — and delivered within — a single release.

[rohitroy]

@varshacpra 

On Enhancement creation from Epics — this is controlled by the sys_property sn_dpr_workspace.auto_create_product_enhancement_for_primary_epic (default: true). If you don't want Enhancements auto-created for primary epics, you can set it to false.

Also, there's a related property sn_dpr_workspace.allowed_states_for_create_auto_product_enhancement that controls which Epic states are eligible for auto-creation (e.g., created, planned, wip, complete).

On your core ask — Enhancement creation directly from Stories is planned for an upcoming release, which should address the scoping flexibility you're looking for.

[varshacpra]

Hi  @rohitroy 

Thank you for the information

The Story-level Enhancement is exactly what we are looking for. Could you let us know:

When is this feature expected to be available?

Is there any workaround we can use until then to split Stories from one Epic into different releases?

This would really help us with our release planning.