Problem

The jira:issueLinkType namespace in the Forge Migrations Mappings API currently only returns DC-to-Cloud ID mappings for issue link types that are directly referenced by at least one migrated issue. Link types that exist in the Jira DC instance but are not used by any migrated issue are excluded from the namespace — even though JCMA migrates all link types to Cloud as part of the instance configuration.

This creates a gap for apps that store instance-level configuration (e.g., issue templates, workflow rules, automation configs) that references link types by their DC ID. When those link types are not used by any migrated issue, the Mappings API returns no DC-to-Cloud ID relationship for them, forcing apps to fall back to unreliable name-based matching.

Suggestion

Extend the jira:issueLinkType namespace to include mappings for all issue link types migrated by JCMA, not only those referenced by migrated issues.

More broadly, consider applying the same principle to other instance-level configuration namespaces (e.g., jira:priority, jira:issueType, jira:resolution) to ensure consistent coverage for app migration use cases.

Current Workaround

App vendors must fall back to name-based matching against /rest/api/3/issueLinkType on the Cloud side. This is unreliable for:

1. Custom link types with non-standard names
2. Instances where link type names were changed between DC and Cloud