nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Why are Atlas Goals visible on JPD ideas to some users and not others?

Stefan Pidzamecky

We have been using JPD and using the "group by" functionality to group timeline view by Goals. This view looks great for me, no empty rows, and all JPD tickets where I would expect to see them (ie. under the appropriate Goal). My permissions on the project is Admin.

For two other users (Creators) looking at the exact same view, they have a very different view where ~40 items do not have goals associated with them.

If I open the exact same JPD idea and look under Goals, I have a goal visible / attached, and they do not.

I am not sure if this is a bug or permissions issue between Atlassian Home vs. JPD. Would appreciate any assistance on resolving this issue.

Accepted answers

Walter Buggenhout

Hi @Stefan Pidzamecky,

My first thought would be permissions. To use goals, users need access to Goals in product admin settings - similar as granting a product license to Jira (but without a license cost).

Hope this helps!

All comments

Walter Buggenhout

Hi @Stefan Pidzamecky,

My first thought would be permissions. To use goals, users need access to Goals in product admin settings - similar as granting a product license to Jira (but without a license cost).

Hope this helps!

Jet_m3qoex

Thanks Walter!

@Stefan Pidzamecky can you please check in 'product access' settings if all users have permission to see goals?

Screenshot 2025-06-12 at 10.19.57 am.png

Please confirm if this solves your issue.

Thank you!

Stefan Pidzamecky

Apologies for the late reply.

It turned out not to be a permissions issue, and a multi-tab caching issue. Logging out, clearing cache, restarting chrome, and logging back in resolved all of the issues of not seeing goals.