Where an idea gets evidence before it gets a team.
The Product Collection packages Jira Product Discovery with Feedback, covering the stage before work becomes committed delivery: ideas, evidence, and what customers actually said. Our work is connecting discovery and feedback to the portfolio roll-up above them.
The Product Collection holds discovery and customer feedback, the inputs to the portfolio. It is in early access, which is itself worth knowing before it is planned around.
What it is
The Product Collection packages Jira Product Discovery with Feedback, covering the stage before work becomes committed delivery: ideas, evidence, and what customers actually said.
It is in early access, so it warrants a different kind of decision than a mature collection. Building a planning process on it now is reasonable; assuming its shape is settled is not.
Where it fits
L2, platform and migration, feeding L3. Discovery decides the portfolio's inputs. Where it is disconnected from the focus areas above it, an organization ends up running two prioritization systems that disagree, and the disagreement surfaces at the worst moment.
What we do with it
Connecting discovery to the portfolio
Ideas that feed focus areas, so intake and prioritization are one system rather than two.
Intake design
A front door for ideas, with the fields that make a decision reviewable a year later.
Deciding whether to adopt now
Early access is a real consideration. We would rather say so than sell a rollout on top of a moving target.
Proof
Four Atlassian Partner Award nominations, 2026: Rising Star Partner of the Year, Americas, and three finalist categories
Atlassian Partner Directory, https://partnerdirectory.atlassian.com/atlas-bench
Questions we get
Should we adopt something in early access?
Where does this sit relative to Focus?
Licensing
Early access changes the entitlement question, so what is included now may not be what is billed later. That reconciliation sits with the rest of the estate in licensing and renewals.