How to automatically roll up Jira issue progress to Atlassian Goals (multi-level hierarchy)?

[#1]

Title:
How to automatically roll up Jira issue progress to Atlassian Goals (multi-level hierarchy)?

Description:

Hi everyone,

I am working with Atlassian Goals and trying to implement a hierarchical goal structure with Jira integration.

My structure looks like this:

• Main Goal

  • Sub-goal A

  • Sub-goal B

    • B1

    • B2

    • B3

  • Sub-goal C

At the lowest level (e.g., B1), I am linking Jira issues (Epics, Tasks, Bugs, Sub-tasks).

Requirement:

I want the progress to work like this:

1. Jira issue status → % (e.g., Done = 100%, In Progress = 50%, To Do = 0%)

2. B1 progress = average of linked Jira issues

3. Sub-goal B = average of B1, B2, B3

4. Main Goal = average of A, B, C

Question:

Is it possible in Atlassian Goals to automatically calculate and roll up progress from linked Jira issues to sub-goals and parent goals?

Or do we need to rely on:

• Manual goal score updates

• Jira Automation / custom fields

• Atlassian Analytics / external tools

Additional context:

I am looking for a scalable solution where goal progress updates dynamically based on Jira issue status changes.

Any best practices, workarounds, or app recommendations would be very helpful.

Thanks in advance! 🙂

[MARS SARID RANGKRUD]

"Linking the progress of a task (Jira) directly to the Goals in a 100% automated manner may lead to a lack of qualitative analysis, because 'task completed' does not always mean 'goal completed'. Having a manual review at the sub-goal level will help the data to be more reliable and reflect the truth."

[Frank Voss]

If you add the Jira work items to the goal and then use the Plans board view and group by goals, it will show the progress for the goal. We use it this way. 

[Damian Dabrowski]

The problem with the Plans board is that there's no goal hierarchy support, so all the Goals are listed alphabetically in a flat structure, rather than Main Goal -> Sub-goals -> Sub-goals, KPIs, etc.

So it certainly helps, but there's still a way to go to make it more user-friendly :)

[mir_contact_stable_point_io]

Hi there,

Great question — this is a common challenge when trying to align Jira execution with Atlassian Goals in a multi-level hierarchy.

 Short answer

At the moment, Atlassian Goals does NOT natively support automatic hierarchical roll-up of progress (from Jira issues → sub-goals → parent goals).

 What works today

1. Jira issue → Goal progress (partial support)

• When you link Jira issues to a Goal, Atlassian can show progress based on issue completion

• This is mainly visible in Plans / Board view

• However:

  • It’s flat (no hierarchy roll-up)

  • No configurable weighting (e.g., 50% for In Progress)

2. No native multi-level aggregation

Your expected model:

Issues → B1 → B → Main Goal

 This kind of nested averaging is not supported out-of-the-box

Workarounds / Approaches

Option 1: Manual + semi-automated (recommended in most cases)

• Use Jira issue progress as input signal

• Keep manual scoring at sub-goal level

• This aligns with OKR best practices (qualitative validation)

 Option 2: Jira Automation + Custom Fields

You can simulate your logic:

• Create a custom % field on issues (or use status mapping)

• Use Automation rules to:

  • Map status → % (To Do = 0, In Progress = 50, Done = 100)

  • Aggregate values at Epic / parent level (limited but possible)

• Then manually sync that into Goals

Limitation: no direct write-back to Goals yet

 Option 3: Atlassian Analytics (best for scalability)

• Use Atlassian Data Lake

• Build a query to:

  • Calculate averages across hierarchy

  • Reconstruct your model (B1 → B → Main Goal)

• Visualize in dashboards

Pros:

• Fully customizable
  Cons:

• Not real-time inside Goals UI

 Option 4: Marketplace apps

Some apps can help bridge the gap:

• OKR tools (e.g., Tability, WorkBoard, etc.)

• Progress roll-up plugins

These often provide:

• Weighted progress

• Hierarchical roll-ups

• Better automation

Best practice insight

As mentioned in another comment, fully automating goal progress can be misleading.

A hybrid model works best:

• Automated signals from Jira

• Manual validation at goal level

This ensures:

• Accuracy

• Strategic alignment (not just task completion)

Conclusion

• No native hierarchical roll-up today

•  Plans view helps but is flat

•  Best approach = hybrid (Automation + manual + Analytics if needed)

---

Curious to know how others are solving this — especially at scale with OKRs 🙂