Description

Please allow the "Choose an Existing Issue" option to be available without needing the corresponding child issue type in the same project. This request addresses the current limitation where the "Create Child Issue" button, and consequently the "Choose an Existing Issue" option, is only visible if the child issue type (e.g., Epic) is included in the same project.

Use Case:

• We create Initiative-level issues in a specific project.
• We want to easily associate these Initiatives with existing Epics from other projects.
• However, we don't want to add the Epic issue type to the Initiative project to avoid the accidental creation of Epics there.

Separating the "Choose an Existing Issue" option from the "Create Child Issue" button makes it easier for users to keep things organized. This way, they can quickly link related issues from different projects right from the Initiative View.

Current Workaround:

The only available workaround is to add the Child issue type to the same project in which the Parent Issues are being created (Issue Type Scheme). This makes the "Create Child Issue" and "Choose an Existing Issue" options visible but introduces the risk of users inadvertently creating Epics in the wrong project, which is not desired.