Programmatic API to link a Jira (Product Discovery) item to a Slack thread and count linked Slack me

[Pierre PM]

We run an automated feedback pipeline: a bot reads every Slack message and creates/triages Jira Product Discovery Feedback items. Today the official "Jira for Slack" integration can sync a Slack conversation thread to a Jira item and count linked Slack messages as Insights — but only when a human triggers it via @JIRA / the message action. There is no public API for either:

1. creating the Jira↔Slack thread link / "synced thread" programmatically (bot-initiated), and
2. creating JPD Insights via the Jira REST API (JPD Insights have no API — confirmed in the community earlier).

As a result, automated bot-created feedback cannot be officially linked/counted as Insights, so teams that prioritize feedback by insight count lose that signal for bot-ingested items.

Requested: Please provide official APIs so an authenticated app can (a) link a Slack message/thread to a Jira item (equivalent of the Jira-for-Slack "sync thread" / "add message to issue" action), (b) create JPD Insights on an idea/feedback via REST (or GraphQL), and ideally (c) have bot-initiated Slack↔Jira links reflect in both surfaces and produce Insights so automation can count them.

Impact: Any team automating product-discovery intake (support bots, MCP integrations, internal tooling) that wants consistent insight-based prioritization. It would let automation produce the same first-class, countable evidence a human produces with one click today.

(See related community threads: "Is it (or will it be) possible to create Insights in Jira Product Discovery via API or MCP?" (June 2026); "Product Discovery APIs" — migrating via REST works but Insights do not.)

[Sami Shaik]

Hi @Pierre PM , here is the honest API-surface map as of today, because the answer is "part of it, and the part you most want is the missing piece."

What the public API does cover. JPD ideas are Jira work items, so the standard Jira Cloud REST API creates and updates them, sets fields, adds comments, and creates work item links (https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/). A bot can create an idea, link it to a delivery work item, and drop the Slack permalink into a field or comment today.

What it does not cover: Insights. There is no public REST endpoint for creating an insight on an idea, and no MCP capability for it either; insight creation is confined to the UI, the Slack and Teams apps, the Chrome extension, and Marketplace apps that integrate through Forge. That is Atlassian's own position as recently as June 2026 on this board: https://community.atlassian.com/forums/Jira-Product-Discovery-questions/Is-it-or-will-it-be-possible-to-create-Insights-in-Jira-Product/qaq-p/3249735. A link added by a bot through the REST API is a link, not an insight, so it will not move the insight count your prioritisation view sorts by. Your read of the gap is correct.

Two cautions before anyone suggests the workaround. JPD's own front end talks to an internal GraphQL service, and people have scripted against it; it is undocumented and unsupported, and Atlassian is already tightening access to it (classic API tokens stop working for some of those queries after 31 October 2026, per the JPD deprecation notice on this Community). Building your Slack bot on it would be building on sand.

What I would do instead, today: keep the bot for what the public API supports (idea creation, linking, comments, a "source: Slack" field), and use the Jira Cloud for Slack app's native "add to idea as insight" action for the human step that actually needs to count as an insight. Then vote for and comment on the public suggestion for an insights write API so the product team sees the bot use case; this thread is a good place to link it once you find or file it.

If you share which prioritisation formula you use, I can suggest a field-based proxy for "bot-ingested feedback" that the REST API can populate and that your view can sort by, so the automated feedback is not invisible while the API gap stands.