It would be helpful to allow an individual release (from a project) to be added to multiple Cross Project releases within Advanced Roadmaps. Currently once a release is added to a Cross Project release it cannot be added to any others.

To elaborate the Our need stems from the fact that a single component release often serves as a dependency for multiple distinct feature initiatives or products, each of which is tracked as its own "cross-project release."
Let's break this down with an example:

• Component Release: This refers to a specific version of a deliverable from a foundational team, like an SDK or a data service. For instance, SDK Release 1.0 or Analytics Release 2.0.
• Cross-Project Release (as per Jira's definition): This refers to a larger, end-user facing initiative or product feature that integrates work from multiple individual projects. For example, Initiatives Widget A for Product #1 or Initiatives Tool B for Product #2.

The Scenario:
Imagine two distinct product features:

1. Feature-123 Widget A (for Product #1): This widget requires SDK Release 1.0 and Analytics Release 2.0 to function.
2. Feature-234 Tool B (for Product #2): This tool also happens to require the same SDK Release 1.0 and Analytics Release 2.0.

In this situation, SDK Release 1.0 and Analytics Release 2.0 are individual component releases. We want to be able to tag both Feature-123 Widget A (first cross-project release) and Feature-234 Tool B (second cross-project release) with these same underlying component releases.
Why this is crucial:
The goal is not to release the component (SDK Release 1.0) twice. Rather, it's to link a single instance of a component release to every higher-level cross-project initiative it impacts or enables.
This functionality gives a single, centralized view to:

• Understand Dependencies: Clearly see which foundational component releases are critical for the realization of various customer-facing features.
• Track Progress: Monitor the progress and release dates of these underlying component releases and how they align with the timelines of the dependent cross-project initiatives.
• Identify Blockers/Impacts: Quickly identify which initiatives might be blocked or impacted if a particular component release is delayed.

In essence, it provides a comprehensive dependency map, showing how various product features and initiatives rely on shared underlying component releases, offering a clear and transparent view of our entire release ecosystem.