API sleekplan and Integration

Description: When the Sleekplan ↔ Azure DevOps integration (or any third-party integration) is active, the Sleekplan API responses do not include the linked external item identifiers (e.g. ADO work item IDs, feature IDs). Problem: Teams that use both Sleekplan and a third-party tool like Azure DevOps rely on the integration to link feedback posts or roadmap items to their backlog. However, when querying the Sleekplan API, the linked external identifiers are not returned in the payload. This makes it impossible to programmatically trace a Sleekplan item back to its corresponding work item — the only viable workaround is to query the third-party system itself and cross-reference from that side, which is indirect and fragile. Benefit: Exposing third-party integration identifiers (e.g. ADO work item ID, external issue key) in Sleekplan API responses would unlock bidirectional traceability. Teams could build automations, dashboards, or AI-powered workflows that seamlessly bridge Sleekplan and their backlog tool — without having to maintain complex reverse-lookup logic on the external side.