Note 03 · 08.10.2026 · Atlassian · Ivar Kaljusaar

Your customers have been talking. Nobody wrote it down.

Atlassian Feedback is the newest app in the Product Collection, with its own breakout at Team '26 Europe this week. The pitch: stop building by hunch. The reality: your customers have been telling Support, Sales and Slack what they want for years, and none of it reached the roadmap. We joined the waitlist.

§ 01

It used to be called Cycle.

Sept 2025: Atlassian buys Cycle, a French feedback-synthesis startup. Founder Mehdi Boudoukhane becomes an Atlassian PM.
May 2026 · Team '26 Anaheim: Product Collection announced: Jira Product Discovery, Feedback, Roadway, with Rovo doing the thinking and Pendo supplying usage data. Feedback goes to early access.
Oct 2026 · Team '26 Europe: Breakout session, a product page, a waitlist. No price, no GA date, no tenant we know of that has it switched on.

Atlassian's product lead, Tanguy Crusson, said the honest thing to press in May: they did not ship a feedback app earlier because the semantic part was not technically possible. Customers describe the same problem in ten vocabularies. Now the model does the merging. Whether it merges correctly is the whole product.

Screenshots in this note are Atlassian's own, from the product page. We have not touched the app yet - that slide comes later.

§ 02

One inbox for everything.

Atlassian Feedback - Recent feedback list with a Zendesk ticket and a Loom clip, Rovo panel answering which enterprise customers shared the most feedback — Recent feedback, unlinked only. Rovo answers in a chart. Screenshot: Atlassian.

Zendesk tickets, Slack threads, Loom clips, Gong calls, Salesforce notes, Pendo, app-store reviews. Every item keeps its source, its author and its customer. Then you ask Rovo a question a PM would ask - which enterprise accounts complained most this quarter - and get a bar chart instead of a Friday afternoon.

Note the filter: "Unlinked only". Feedback that is not yet attached to an idea is the backlog. That is the job.

§ 03

Insights, not tickets.

Atlassian Feedback - Voice of customer dashboard with highlight cards, top insights table, impacted customer segments donut and a feedback stream — Voice of customer. 3,220 items, six insights, four segments. Screenshot: Atlassian.

The AI groups raw feedback into insights - "user is confused by onboarding steps", 117 votes - and tags them by pattern, segment and trend. The highlight cards are the interesting bit: "navigation" complaints down 42%, "can't find feature" up 67%. That is the sentence a PM wants in the Monday review, and today someone writes it by hand from a spreadsheet, if at all.

§ 04

The wire into JPD.

Jira Product Discovery impact assessment view with a Feedback column, and an idea showing three linked feedback items from Slack, Zendesk and Pendo — Jira Product Discovery, Impact assessment view. The Feedback column is new. Screenshot: Atlassian.

This slide is where the money is. An insight becomes an idea in Jira Product Discovery, the idea carries its feedback count, and every item still links back to the human who said it. When the idea ships, Feedback can tell those humans. Feedback without JPD is an inbox. JPD without Feedback is a guess. Atlassian is selling the pair, and the Collection licence will reflect that.

If you are on JPD Free or Standard, expect this to be the reason to look at the Enterprise tier.

§ 05

What it isn't.

Not priced: No number on the page, no number in the session, no number from our partner contacts. Product Collection pricing is the thing to watch, not the app.
Not available: Early access since May, waitlist since this week. Expect months, not weeks, before it appears in an EU tenant.
Not a survey tool: It reads what already exists. If your customers only talk to you through a web form, there is nothing to ingest.
Not the whole loop: "Close the loop" is a notification when an idea ships. Release notes, changelogs and the public roadmap are still your problem, or a Marketplace vendor's.

The Marketplace vendors who sold feedback-to-JPD plumbing have read the same page we did. Watch the Released and Canny roadmaps this winter.

§ 06

Who should care.

Product teams on JPD: You are the target. Join the waitlist now, because the first wave will be existing JPD Enterprise customers, and tidy your idea structure before it arrives. The insights will land on whatever hierarchy you have.
Support and Sales leads: Your tickets and call recordings become product evidence without you summarising them. Decide today what the PMs may and may not read in a Gong transcript.
Jira admins: Another set of Rovo connectors with read access to Zendesk, Slack, Salesforce and Gong. Same inventory, same ownership and same EU-inference questions as every agent we wrote about yesterday.

Small teams: the useful question is not "do we need Feedback" but "where does our feedback go today". If the answer is three Slack channels and someone's memory, the app is not the fix. The habit is. The app just makes the habit cheap.

§ 07

What we'll do with it.

Kvitsung, our own expense product, has feedback in exactly the wrong places: support mail, two Slack channels and a Jira project nobody links to anything. It is the perfect guinea pig. When the waitlist opens, it goes in first and this note gets a part two with real screenshots.

If you run product on Jira Product Discovery and want your Support and Sales feedback wired into it before Atlassian's app does it for you - or want the connectors and permissions sorted so it can - that is a Tuesday for us. Contact: hello@techodesk.ee

Sources: atlassian.com/software/feedback · Team '26 Europe breakout "Stop building by hunch", 06-08.10.2026 · Atlassian blog, "Cycle joining Atlassian", 09.2025 · diginomica, Team '26 coverage, 13.05.2026. Screenshots © Atlassian, used for commentary. Beaconstone, Vitafleet and Stackies are Atlassian's demo customers, not ours.