Show linked Jira tickets directly under each Goal in the Jira Software "Goals" tab

[Edward Martin]

Hello,

I'm using the Goals tab in Jira Software, which displays our Atlas goals along with their latest status update. Currently, clicking on a goal redirects to Atlas, without showing the linked Jira tickets (Epics/Initiatives) directly in Jira.

My question/suggestion: Would it be possible to display, directly under each goal in this tab, the list of linked Jira tickets (with their status), without having to leave Jira to check Atlas or manually filter a List view using the Goals field?

This would allow for a much quicker overview of the actual progress of work tied to each goal, right from Jira Software, which would be especially useful for PMO/portfolio management teams tracking multiple initiatives in parallel.

Is this feature already on the roadmap, or is there an existing way to achieve this that I may have missed?

Thanks in advance for your input!

[James Gamble · Accepted solution]

Hola Edward,

What you’re describing isn’t available in the Jira Goals tab today. That view shows the Atlassian goal and its status information, but it doesn’t expand each goal to show the Jira work items linked through the Goals field. Your screenshot and description match that current behavior.

The native Jira option today is still to work from the Jira side and use the Goals field in a List view to see which work items contribute to each goal. Atlassian documents linking and viewing goals from Jira here.

Since you’re on Standard, Plans isn’t available as another roll-up option. Plans on Premium can filter work by goal and give portfolio teams a broader hierarchical view, but it still wouldn’t turn the existing Goals tab into the expandable goal > linked work items view you’re asking for.

I couldn’t find a public Atlassian roadmap item specifically for displaying the linked Epics or Initiatives directly beneath each goal in that tab. I’d suggest submitting this as a feature request, with the PMO use case you described.

Thanks,

James

[Edward Martin]

Thank you very much for the answer!