compass.yml files merged to repo but no components appearing in Compass dashboard — seeking guidance

Question

We created 30 compass.yml files (one per microservice) across our GitHub monorepo github.com/priv8pay/travel and merged them into the 0.14.0.0 branch via PRs #6338, #6410, #6426, #6433, #6443 (merged Feb 24 – Mar 12, 2026).

Each file follows this structure (example from services/billpay/srv/compass.yml):

name: billpay
description: Bill pay service managing payee setup, payment scheduling, and execution
ownerId: ari:cloud:identity::team/ABCD
typeId: SERVICE
lifecycle: ACTIVE
labels:
  - domain:billpay
  - language:java
  - runtime:docker
fields:
  tier: 1
links:
  - name: GitHub Repository
    type: REPOSITORY
    url: GITHUB URL pointing to 0.14.0.0
  - name: OpenAPI Spec
    type: DOCUMENT
    url: GCS bucket url where specs are stored

All 30 files use:

* typeId: SERVICE
* lifecycle: ACTIVE
* ownerId: ari:cloud:identity::team/ABCD

What we expected

The services to appear as components in the Atlassian Compass dashboard automatically after merge.

What we see

Nothing — the Compass dashboard shows no components from our repo.

Our default branch is develop, but our compass.yml files are currently on the 0.14.0.0 branch. Does the app only scan the default branch? Is there no option to customize this ?

Tinker Fadoua · Answer

Welcome to the Atlassian Community @Raghavendra Rao I 0.14.0.0 if you can make it your default branch then you will be good otherwise it is the problem. Sometimes the way we configure things in repos can go against us. Once your release is over I will suggest to take care of this problem so it won;t happen again. Please update us if your issue has been resolved.

Tomislav Tobijas · Answer

Got it @Raghavendra Rao I . Thanks for clarifying!

I'm still exploring this area, specifically regarding general DevOps and how Compass (can) work. That being said, I don't have a clear answer to your question, but as stated above:

...If not, you could reach out to Atlassian Support,...

You could reach out here. Note that you'll need at least one paid subscription (if you have a Compass paid plan, that would help).

Anyway, the team there should definitelly know more and offer some alternatives and potential workarounds you could use. Also, they should be able to raise a new feature request based on your requirement.

As additional resource (if no one chimes in here), you could check and reach out to Developer community - Compass category and see if folks there know more about this 🤔

Cheers,
Tobi

Raghavendra Rao I · Answer

Hi @Tomislav Tobijas ,

Thanks for the quick response! That explains it.

A bit of context on why both options are tricky for us:

* 0.14.0.0 is our active release branch — it's not a feature branch, it's where our current release lives. Merging it into develop right now would pull in changes that aren't ready for the next dev cycle.
* Changing the default branch temporarily carries risk for our CI/CD pipelines, GitHub PR targets, and automated workflows that all reference develop as the default.

What I'd really like to ask:

Is there any way for the Compass GitHub integration to be configured to scan a specific branch (e.g. 0.14.0.0) rather than only the default branch? Even a one-time manual rescan of a named branch would unblock us.

If that's not possible today — could you point me to where I can raise this as a feature request? Specifically: "Allow configuring which branch(es) Compass scans for compass.yml files, per connected repo." This seems like a common need for teams using release branches or trunk-based branching strategies where the default branch isn't always the most stable/current.

In the meantime, is there any workaround — such as the Compass REST API or a CI-pushed sync action (atlassian/compass-component-sync) that we could use to push component data from 0.14.0.0 without depending on the default branch scan?

Thanks again!

Raghavendra