# Everyone's finally using Atlassian Goals. Here's where it still breaks.
> Jira Goals adoption is finally taking off. Here's what the Atlassian Community keeps hitting — and how Strategy Hub addresses each gap.
Canonical: https://caskcode.io/blog/everyone-s-finally-using-jira-goals-here-s-where-it-still-breaks/
By Bartosz Wyszkowski · August 18, 2026
As a founder of [caskcode.io](https://caskcode.io/), I spend a fair amount of time reading the Atlassian Community — partly because it's genuinely useful, partly because it's the clearest signal I know of for what people actually need versus what they say they need in a sales call.
**Atlassian Goals is having a moment, and it deserves it**
More teams are putting their strategy directly inside Jira instead of a separate deck or spreadsheet, and the reasoning shows up constantly in community threads: Jira is where the work already happens, so goals living anywhere else quietly stop getting looked at. Keeping objectives, key results, and the actual tickets that move them in one place is the whole point — it turns "we set OKRs in January" into something people can check against reality in June.
Atlassian has clearly been investing here too. Over the past year they've shipped goal-level progress metrics, configurable Goal types so teams can use their own terminology instead of Atlassian's, and most recently more flexible rollup options. That's real progress, and if your organization hasn't tried using Goals to cascade strategy into Jira work yet, the case for it is stronger now than it's ever been.
**But read enough threads, and the same structural walls keep coming up**
Here's what people are actually asking for — and hitting limits on — in their own words on the Goals and Projects forum.
_No real distinction between a strategic goal and a team-level one._ One recent thread posed the question plainly — does Goals support a strict parent/child hierarchy, with org-level Strategic Objectives as the explicit parent of team-specific quarterly OKRs? Nobody in that thread said yes. The clearest articulation of why came from Viktoriia Golovtseva, a Community Champion active on the Goals forum, responding to a related point in the same discussion: deep goal hierarchies look impressive in planning decks but collapse under maintenance overhead. That's the real shape of the problem — Goals lets you nest anything under anything, but nothing in the structure tells you "this level means strategic pillar" versus "this level means this quarter's team OKR." The depth is available; the meaning isn't.
_Rollup forces an either/or that doesn't match how orgs are actually shaped._ Atlassian's own rollup update lets a goal pull progress either from its success measures or from its sub-goals — not both. One person's feedback on that thread laid out exactly why that's a problem: if a department has its own success measures sitting between company objectives and team sub-goals, you'd have to create an extra sub-goal just to contain the department-level measures, which then sits at the same hierarchical level as team sub-goals even though it isn't one. Atlassian's own response confirmed this is still a backlog item, not a shipped feature.
_Jira issue progress doesn't roll up through the hierarchy automatically._ This is the one that surprises people most. A developer working through the Forge community confirmed it directly: as of now, Atlassian Goals does not natively support automatic hierarchical roll-up of progress from Jira issues, through sub-goals, to parent goals. If you've built out Goal → Sub-goal → Sub-goal → linked issues expecting the top of that tree to reflect the bottom automatically, it doesn't — someone has to update it by hand at each level, or you're building your own automation to bridge it.
_Seeing the whole cascade means leaving the tool._ This one shows up constantly: teams with a handful of interlocking OKRs across a division end up exporting everything to spreadsheets or mind-mapping tools just to see how it all connects, because the native table view doesn't show cascade relationships well once you're a few levels deep.
_"Framework-agnostic" mostly means "no framework at all."_ Goal types let you rename things — call it an OKR, a Big Rock, whatever fits your language. What it doesn't do is give you a structure that already knows the difference between an objective and a key result, enforce how many of each you should have, or apply any of the well-known planning frameworks out of the box. You get freedom to name things; you don't get a framework doing any of the thinking with you.
None of this is a knock on the Atlassian team — the rollup and Goal Types work landing recently shows they're actively chipping away at exactly these threads. It's just not there yet, and if your org needs it now, that gap is real.
**Where Strategy Hub picks this up**
This is close to the exact list I had in mind before I wrote a line of code, so it's worth being specific about how [Strategy Hub](https://marketplace.atlassian.com/apps/4032874960/strategy-hub-okrs-goals-kpis-strategy-planning-for-jira?hosting=cloud&tab=overview) addresses each point above:
- **Typed hierarchy, not just nesting.** Strategy Hub lets you define actual Types — Strategic Pillar, Department Goal, Team OKR, whatever your org calls its levels — so "this is a strategic objective" isn't just a deeper indent, it's a distinct kind of Item with its own place in the structure. That distinction carries through the rest of the app: the Portfolio board gives you a helicopter view scoped to just your top-level Strategic Objectives, filtered away from the team-level noise underneath them, and dashboards can be built per Type — so leadership gets a dashboard of strategic pillars while a department head gets one scoped to their own goals, without either group wading through the other's detail.
- **Rollup from linked Jira work, automatically, through every level.** Progress on a Key Result rolls up to its Objective, which rolls up further, weighted by story points or priority rather than a flat count — no manual updating at each layer.
- **Views built to show cascade, not just a flat table.** Portfolio board, Team board, Roadmap, and a dedicated Hierarchy map — so seeing how a division's OKRs connect doesn't require exporting to Sheets.
- **Actual frameworks, not just renamed fields.** Eight starting presets built around known planning frameworks, with every Type, Status, and level fully reconfigurable afterward — a structure that does some of the thinking, that you can then make your own.
If you've hit any of the walls above, I'd genuinely like to hear about your specific setup — what your hierarchy actually looks like, and where it breaks. That's exactly the kind of feedback that shapes what gets built next.
[Try Strategy Hub on the Atlassian Marketplace →](https://marketplace.atlassian.com/apps/4032874960/strategy-hub-okrs-goals-kpis-strategy-planning-for-jira?hosting=cloud&tab=overview)