Compass Scorecard – Incorrect "Needs Attention" Count and Duplicate Components

Question

Hello everyone,

I’m facing an issue with a scorecard I created in Atlassian Compass and would appreciate any help.

I built a scorecard to monitor obsolete providers (jboss, websphere, and standalone) across components. Additionally, I need to identify components where the custom field "provider" is not filled in.

There is also a requirement to exclude components related to libraries. For that, I applied filters to remove components with *lib + static before evaluating the criteria.

Expected Behavior

* Components with provider = jboss | websphere | standalone → Failing
* Components with no value in the provider field → Needs Attention

Current Behavior

* The Failing count is correct (64 components).
* However, the Needs Attention count is incorrect (showing 1385 components).
* In the scorecard component list, I can see multiple duplicate component entries, which seems to be inflating the count.

What I Tried

* Created a scorecard filtering only non-library components:* type = service
* cicd-recipe ^ *lib + static

* Defined two criteria:* provider = jboss | websphere | standalone → Failing
* provider = has any value

* Validated the real scenario using manual filters:* Needs Attention (expected):* Type = application
* Provider = not set
* cicd-recipe excludes *lib + static

* Failing (confirmed correct):* Type = application
* Provider = jboss | websphere | standalone
* cicd-recipe excludes *lib + static

The manual filtering confirms that the failing count is accurate, but the "Needs Attention" count from the scorecard is much higher than expected.

Question

Has anyone experienced a similar issue with duplicated components or incorrect counts in Compass scorecards? Is there something I might be missing in the criteria configuration or filtering logic?

Any guidance would be greatly appreciated!

Anwesha Pan · Answer

Hi @Martins de Lima 👋🏻

First of all, welcome to the community! ✨

Thanks for the detailed breakdown of your scorecard setup. Based on the conversation in this thread and what's been confirmed (same component IDs appearing multiple times), this looks like a backend indexing/sync issue rather than a misconfiguration on your end. You could try the following perhaps if not tried already:

Steps to try:

Verify duplicates are truly the same object — You've already confirmed this by checking component IDs. That rules out accidental duplicate component creation.

Check if the custom field "provider" is consistently indexed — Since it's a custom dropdown field, confirm it's enabled and populated consistently across all component types in your scorecard filter. Inconsistent field availability can sometimes cause unexpected scoring behavior.

Contact Atlassian Support — Since this is a confirmed system-level issue (not a config problem), the fastest path to resolution is raising a support ticket so Atlassian can inspect the backend index for your org. If you're on a paid Compass plan (Standard or Premium), you can do this directly. If you're on the free plan, you may need to start a trial to access support.

Check the Atlassian Community for similar reports — It's worth searching for other Compass scorecard indexing issues to see if there's a known workaround or a fix already in progress.

Hope that helps! 🙂

Thanks,
Anwesha

Tomislav Tobijas · Answer

@Martins de Lima, thanks for the clarification. Based on this:

I checked the component IDs, and they are the same in all the cases I found. For example:

...compass/component/e945d15f-xxx2-4cbc-80aa-blablabla

it seems like it's a system issue rather than a config issue.

Which Compass plan are you using? If you're on a paid plan, I'd recommend reaching out to Atlassian Support with this for them to check the backend. If you're on a free plan, you could start a free trial of Standard or Premium just to raise a ticket and then downgrade once they troubleshoot this. 👀
It's definitelly the easiest (and probably the quickest) method to check what's going on here.

Btw, I did a quick check on reported issues and suggestions here, but I couldn't find anything related. Although you could take another look and see if there's potentially something that matches the behavior you're seeing 👀

Martins de Lima · Answer

Hello, @Tomislav Tobijas

Thank you for your attention.

"Provider" is a custom dropdown field, and yes, it is enabled for all components.

I checked the component IDs, and they are the same in all the cases I found. For example:

...compass/component/e945d15f-xxx2-4cbc-80aa-blablabla

Tks