Atlas Goals field not visible on Issues in Backlog view of a Jira Projects

[Gabor Horvath]

Hello, in Jira Software Cloud, I've added the Goals field under the card layout menu in the Board Settings to make it visible in the Backlog view (there are 3 additional fields that can be selected for this purpose). Despite of this, tickets where this Goal field is filled out still show "None" in the Backlog view.

Troubleshooting already taken
1. Goals field is properly enabled in the Jira Project and is linked to the relevant work items.
2. The Backlog view is configured to display the Goals field.
3. I've refreshed the page several times, and even a few days passed since the setup to account for any synchronization issues.
4. I have the necessary permissions to view the Goals field because I'm a Jira admin.

I've read the documentation about syncing Atlas with Jira but wasn't aware of any further steps.

What could be wrong with the Atlas integration? Thank you for any advice on this.

[Sarah Navin]

This behavior is actually expected at the moment, it isn’t a configuration issue on your side.

Short answer

Atlas Goals are not yet supported as a data source for the "Card Layout > Additional Fields" on the Backlog view.

Even though the field appears in the dropdown list, the Backlog/pool issue cards cannot currently render Atlas data, so Jira shows "None" for all issues.

This has confused a lot of users because the UI implies the field should work, but the integration isn’t fully implemented across all board and backlog views.

Why this happens

Atlas > Jira integration works in these places today:

• Issue view (in the right sidebar)

• Search (JQL: goal = <id>)

• Issue navigator columns

• Board cards (Kanban/Scrum board view only, not Backlog) – but even here, loading is sometimes delayed

However, the Backlog view uses a separate rendering pipeline, and Atlas fields are not yet retrieved there. As a result:

• The field appears in settings

• The issue has a valid Goal set

• Permissions and syncing are fine

• But the Backlog view cannot display Atlas fields

How to confirm it's the same issue

Try switching your board to the Active Sprint / Board view and add Goals there.
You’ll notice that the Goal will appear correctly on cards — only the Backlog view fails to load it.

Workarounds (for now)

Until Atlassian extends Atlas-field support to the Backlog view:

1. Use the Epic panel or custom fields
   Some teams temporarily map Goals to a normal custom field for backlog visibility.

2. Add Goals to the Issue Navigator column layout
   This at least gives you list-level visibility.

3. Use Atlas’ own filters/dashboards to track Goal alignment
   This avoids depending on backlog rendering altogether.

[Greg D]

Hi @Sarah Navin , is this close to being fixed? The workarounds do not function to help with rituals/ceremonies within sprints and kanban. The Epic level is lower than a Goal level.

We’ve been leaning heavily into Atlas Goals as the “above‑epic” layer for OKRs and ran into a pretty sharp edge in Jira Software boards/backlogs.

What we did

• Linked Epics (and sometimes stories) to Atlassian Goals per this doc:
  Link work in Jira to goals and projects in Atlassian Home | Jira Cloud | Atlassian Support
• On our cross‑project Scrum board
  
  • Added Goals to the backlog and active sprint card layout.
  • Tried to create swimlanes by Goal using JQL on the goal field
  • Tried to create a quick filter on a Goal

What we expected

• Cards in Backlog / Active sprint would show the linked Goal(s), like any normal field.
• Swimlanes using the goal field would reliably group issues so we can run sprint rituals “by Goal” (above Epic) across multiple projects.
• Quick filters would filter everything on a board based on that JQL or a canned Goals field selection

What actually happens

• Backlog:
  • “Goals” is selectable in card layout, but cards always show None even when the issue is linked to an Atlasian Goal.
• Active sprint:
  • Goals rendering on cards is inconsistent at best... you also cannot pick that as a Card value.
• Swimlanes / filters:
  • JQL on goal works in the Issue Navigator
  • But the same JQL doesn’t reliably surface matching issues in board swimlanes

That makes it impossible to use Goals as a practical grouping mechanism during ceremonies, even though the UI suggests it should work (field present in card layout + JQL support).

I’ve raised this with Atlassian Support and mentioned this public JAC issue that is similar:
https://jira.atlassian.com/browse/ATLAS-154

From a user perspective, this feels like one of:

• A bug (field is configurable but not actually supported in backlog/board rendering), or
• A missing feature where the UI is ahead of the underlying integration.

Either way, if anyone else is trying to:

• Group sprint work by a level above Epic, and
• Use Atlassian Goals for that on a single cross‑space board,

...you’re likely to hit the same limitation.

Plans are a slightly different use-case and it is hard to group things on boards properly that are driving OKRs/Goals (especially for teams that run cross-space work in their boards).