Does the Goals feature have a future?

[Carlos Garcia]

My organization is starting to track OKRs and other more losely defined goals for Product Management.

In Principle the "Goals" feature at Atlassian Home does just what we want in essence, but it still feels way too immature as a feature. Some examples include:

1. There are no automations, nor API access to manage goals programatically and updates.
2. The support for goals @ "Plans" (a.k.a. "Advanced Roadmaps") is rather rudimentary (for example, Goal hierarchy is ignored when grouping things by goal)
3. Linking with Jira items is still rather clunky.
4. Navigating nested goals is hard, unless you always go back to the "home" page. For example, on the "child goals" in the sidebar you cannot see assignees or timeframes.
5. Learnings, Risks and Decisions live in isolation, and are not shown in e.g. the CSV exports
6. Better exports or better visualization alternatives for various reporting and planning contexts could be very helpful.

We could live with the current state for a few months, provided we knew that there will be constant improvements... but at the same time, I can barely find any plans for Goals in the Cloud Roadmap. 

Knowing that this product is not being monetized independently or as part of some premium package, and lacking any evidence on planned improvements, I'm extremely hesitant to pour all my OKR planning, and teach my POs and stakeholders to use this tool. Can anyone at Atlassian shed some light regarding what to expect with the future development (or lack thereof) for Goals please? 

[Matteo Vecchiato]

Hi @Carlos Garcia ,

Good point. My reply is not going to give a response to your question, but the goal is one of the basis of the new "System of work" by Atlassian: system-of-work 

I hope this feature will be exploded more in the future.

Regards

[Carlos Garcia]

Thanks for the hint!

[Ariel Yadin]

@Carlos Garcia, you've articulated exactly the friction point most teams hit. The Goals feature is conceptually sound but operationally half-baked. The lack of API access alone is a dealbreaker for any team that wants to automate status updates or pull OKR data into dashboards without manual effort.

The point about Plans ignoring goal hierarchy when grouping is particularly painful. You end up with a roadmap view that looks organized but doesn't actually reflect how your OKRs cascade — which defeats the purpose.

Honestly, the 'System of Work' framing from Atlassian is encouraging directionally, but that's a vision statement, not a shipping commitment. I wouldn't block your OKR rollout waiting on it.

What's worked for some teams I've seen: keep Goals as a lightweight linking layer in Jira, but run the actual OKR tracking in a dedicated tool that has proper hierarchy, check-in workflows, and reporting. Bazz OKR  is one worth evaluating if you're staying in the Atlassian ecosystem. It handles the hierarchy and Jira linking more robustly.

Happy to share more on how other product teams have structured this hybrid approach if it's useful.