Add an API endpoint (or option) to create/link an integration record (e.g. Aha ↔ Jira) with use_remote/“commit from Jira” behavior, so Jira can overwrite/sync the Aha entity on initial link—matching what the UI supports.

What is the challenge?

• The current API does not support programmatically creating an integration link and selecting the “use_remote / commit from Jira” option in the same flow (or at all), so the UI can do something the API cannot.

What is the impact?

• Automation is blocked: linking Aha features to Jira issues and enforcing “Jira as source of truth” can’t be done in scripts/integrations.

• Leads to manual UI work, inconsistent sync behavior, and higher risk of data drift between Aha and Jira at scale.

Describe your idea.

• Introduce an API capability (e.g., a new integration_links endpoint or an enhancement to existing integration-field/link endpoints) that allows clients to create the link between an Aha record (e.g., feature) and a Jira object and explicitly choose the initial sync direction (e.g., use_remote=true / commit=remote), triggering an immediate “pull from Jira and overwrite Aha” operation equivalent to the UI workflow.