Support the ability to visualize release calendar using set or derived end dates

What is the challenge?

• The release end date calendar report uses two different end-date concepts at the same time. The report filters releases based on the explicit end date in the release date range, but the monthly grouping logic uses a calculated end date derived from related features and release phases

• This inconsistency can cause releases to be grouped into a different month than the one implied by their configured release end date, which means some releases do not appear where customers expect them in the calendar report

What is the impact?

• Customers can see missing or incorrectly grouped releases in release end date calendar reports

• This is especially confusing because the release date range is customer-configured and is what customers expect reporting to reflect

• Support has already reproduced the issue, and the inconsistency makes calendar reporting feel unreliable

Describe your idea.

• Update the release calendar report to support both set and derived release end dates, with clear behavior for each scenario

• For calendar reporting, use the release’s explicit date range end date when one is set so releases are grouped and displayed consistently in the month customers expect

• For releases without an explicit end date, continue supporting a derived/calculated end date for scheduling and capacity-style use cases

• The UI may need a clear interaction for toggling or choosing which end date perspective is being used, but the core requirement is to eliminate the current inconsistency and ensure customers can visualize releases using either set or derived end dates