Using automation, allow features and requirements to inherit a Rollup release name

What is the challenge?

Roll up releases are ideal to synchronize releases of services within a platform. As an example, on Service A and Service B in Platform A are both released on the same schedule.

Our developers work within Jira and Devops, and we need to effectively communicate to development which features of which service (and child requirements) are being targeted for which platform release (roll up release).

We can of course point them to a view within Aha, however, development live inside of the chosen development platform of choice and therefore create their own views and queries. It would therefore be idea to allow automation to assign the rollup release name to any child feature and requirement of that release

What is the impact?

Forcing development into Aha, although ideal is not practical. Aha should work to provide as much information as possible to whatever development platform development choose to use.

Describe your idea

Allow automation to assign the roll up release name to any feature and requirement that has been assigned to that rollup release.

Features are already grouped into rollup releases when viewing the roadmap of a product line, so the association already exists, automation needs access to this association