Release to be optional on Epics, or multi-select

What is the challenge?

In the admin configuration for a workspace, Aha! provides a tooltip explanation for "Epics", which reads:

"What are epics?

Epics are used for bigger work items and can be used to group together many features, which can span multiple releases....."

However, the "Release" field at the Epic record is mandatory, and single-select.

If we have to set a singular release value on an epic, this can and probably is contradictory to that epic housing features which were delivered across multiple releases.

What is the impact?

1. Inconsistency in Gantt chart functionality Aha! provides OOTB

   1. Example: Suppose I have an epic containing 3 features. Those 3 features will be delivered across 3 upcoming releases. I would have to arbitrarily choose one of these releases to be set on the Epic (presumably the last).

   2. Now suppose I am trying to utilize the Gantt chart to draw out dependencies for these features. When using the "Releases, Epics, Features", I cannot get a visualization of these 3 features. The Gantt chart only displays the feature which has the same Release value which is set on the Epic. I won't see the other 2 features in the Gantt chart.

2. The mismatch of release between Epics and Features does contribute to general data inconsistencies in reports. There may always been a need to either:

   1. Explain the discrepancy

   2. Create an Epic / Feature structure where the features must match the release of the epic.

Describe your idea

"Release" value set on the Epic should either be:

1. Multi-select, so that more than one release can be selected

2. Optional