RFC-153 Forge Extensibility for Goals & Projects

RFCs are a way for Atlassian to share what we’re working on with our valued developer community. It’s a document for building shared understanding of a topic. It expresses a technical solution, but can also communicate how it should be built or even document standards. The most important aspect of an RFC is that a written specification facilitates feedback and drives consensus. It is not a tool for approving or committing to ideas, but more so a collaborative practice to shape an idea and to find serious flaws early.

Please respect our community guidelines: keep it welcoming and safe by commenting on the idea not the people (especially the author); keep it tidy by keeping on topic; empower the community by keeping comments constructive. Thanks!


Summary

Goals & Projects connects strategy to execution across Atlassian. This RFC proposes making Goals & Projects extensible with Forge so developers can add contextual experiences, read and update goal and project data, and integrate with systems that hold delivery, financial, and operational information.

  • Publish: 26 October 2026

  • Discuss: 9 November 2026

  • Resolve: 16 November 2026


Problem

Customers track their goals and projects through the Atlassian Goals & Projects apps, while the data that shows whether those goals and projects are succeeding often lives elsewhere, such as a CRM, BI tool, finance system, Jira, or governance platform. Today, customers cannot:

  • Add external context, such as delivery risk, approvals, or financial information, to goal and project pages.

  • Keep goal progress updated automatically when the source data changes.

  • Connect information across Goals & Projects, Jira, Confluence, Teams, and external systems in one experience. Connecting Goals & Project to the Forge Global App (in EAP) could be a way forward.


Proposal

Enable Forge extensibility for Goals & Projects by:

  1. Defining extension points such as panels, tabs, cards or fields

  2. Providing APIs and context for apps to access for example goal metrics and updates securely

APIs and permissions proposal

Scope

What it allows

read:goal

Read a goal’s name, status, score, owner, due date, success measure, and linked projects.

write:goal-metric

Update the current value of a goal’s success measure.

write:goal-update

Post a status update on a goal for its owner.

read:project

Read a project’s status, owner, target date, contributors, linked goals, and linked work.

write:project-update

Post a status update or raise a risk on a project.

Example use cases

The following examples are supported by the available design artifacts. Screenshots can be added below each example.

Example 1: Keep a goal’s success measure up to date

A revenue app reads a goal using read:goal and updates its success measure every hour from a CRM report using write:goal-metric. Each week, it posts a status update for the goal owner using write:goal-update. The goal page remains native, while the CRM connection is represented in a compact goal context experience.

Example 2: Delivery risk and approval stages on a project

A governance app reads a project and its linked Jira work using read:project to calculate a delivery confidence score. It tracks approval stages alongside the project and lets approvers complete sign-off from the project experience. The app posts the outcome and any risks back to the project using write:project-update.

Example 3: Cross-app portfolio view with Global Apps

A Forge Global App (EAP) installed once at the unit level and connects to Goals & Projects, Jira, Confluence, and Teams). It provides a portfolio view showing each goal with its projects underneath. For each project, it displays status, Jira progress, the owning team, and linked Confluence pages.

Asks

  1. APIs and permissions: What extension points would be most useful to your customers? Which goal and project data do you need to read or write first?

  2. Use cases: What would you build first, and for which customers?

  3. Governance: What controls do administrators and goal owners need over apps that write to goals and projects?

How to give feedback

  • Comment directly on this RFC thread in the Atlassian Developer Community.

  • Share use cases, concerns, and suggestions to help shape Forge extensibility for Goals & Projects.

Hi @JuliaDaehne

Thank you for making Goals & Projects extensible. The scopes and use cases are a good start, and many of the ideas already fit what we see.

  1. APIs and permissions
    We miss events. Apps need to get notified about goal and project updates and metric changes, so data can flow to other systems without polling. Product events (or webhooks) for status, owner, target date, metric value and linked work changes would cover this.

We also have a question on progress calculation. If a goal’s progress is calculated from its key results, can custom metrics written by an app count into the calculation of the parent goal? That would make external metrics (CRM, finance, BI) first-class.

Next to this, we need MCP support. The reporting and aggregation that already run in Goals & Projects should be reachable through MCP and Rovo, with the same permissions.

  1. Use cases
    Connectors to BI tools and data lakes. They need read access to goals, projects and metrics, plus events to keep the data current. Metric sync from external systems into goals is the second case.

  2. Governance
    We have no specific ideas yet.

Cheers
Oli

Hi @JuliaDaehne,

Great to see APIs for Goals & Projects becoming a reality. This is a big unlock, and I expect it to drive a lot more adoption of Goals & Projects, because teams will be able to bring them into the tools they already work in.

+1 to @oliver.straesser’s request for events or webhooks. We’d like to be notified of any change to a goal or project, so the data in our app stays current without polling.

A few other things that come to mind:

  • Linking APIs to link/unlink Goals and Projects with Jira work items, and Projects with Goals.
  • Inclusion of visual identity metadata, including emoji, icons and colours for both Goals and Projects, so users can recognise them consistently across native and app experiences.
  • Bulk reads and paginated search, including filtering by status, owner and linked work.
  • Complete read data, including current health status, posted updates, descriptions, target-date precision, icons and canonical URLs.

Cheers,
Jens

Hi, Great to see this RFC! :tada:

Apps also need to discover goals and projects:

  • read:goals: return a list of goals based on criteria. We need name (for search), owner, status, parent goal, team, tag, priority, start date and target date.
  • read:projects: return a list of projects based on criteria. We need tag, status, goal, team, owner and contributor.

Sorting and pagination should be part of the design.

Fields on the goal & project

  • read:goal: add parent goal, child goals, team and updates.
  • read:project: add team and updates.

Updates should work in two modes: as the app and as the user.

-Janette

Hi @oliver.straesser MCP support is covered through MCP v2 today! Tools list: Supported tools | Atlassian AI Gateway | Atlassian Support

Hi @JensSchumacher1 , I wonder if your linking use case could be achieved through a unit installed Forge app that can optionally link to one or more Atlassian apps in a customer’s unit.
We will start EAP later this week https://developer.atlassian.com/changelog/#CHANGE-3523

Hi @JuliaDaehne, not sure I understand the linking suggestion. In our case, we would want to link a Jira work item to a goal from within Jira. Does that make sense?

Ah, I missed this scope change in V2 :slight_smile: Just metrics can’t be read through it. But thank you for the hint!

By the way, we’ve recently added support for Goals and Projects to one of our Apps. But it was done through the Teamwork Graph, and as such it’s read only.

Happy to take you through the use-cases for it @JuliaDaehne.

Yes that makes sense. If you only need to create a link from inside Jira, a normal Jira Forge app that calls goals_linkWorkItem may be enough.

Would love to see it @JensSchumacher1 !

Thank you to everyone who contributed use cases, questions, and feedback on Forge extensibility for Goals & Projects. It has helped us better understand the opportunities and requirements in this space.

We’re closing this RFC with the feedback captured here as input to further exploration and prioritisation. We’re considering this area in the context of broader Forge and Global Apps work.