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

[Martins de Lima]

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

1. Created a scorecard filtering only non-library components:
   • type = service
   • cicd-recipe ^ *lib + static
2. Defined two criteria:
   • provider = jboss | websphere | standalone → Failing
   • provider = has any value
3. 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!

[Tomislav Tobijas]

Hi @Martins de Lima ,

Quick question - "provided" is a custom field of which type? 
Also, I'm guessing that this custom field is explicitly enabled for all Component types included in your scorecard filter?

I do know that in some Atlassian apps, "None" or incorrect counts can appear to sync issues between the database and the search indexes. 

👀 One thing you could check (to see if there's potentially a system issue) - pick a couple of duplicate entries in the scorecard list and check component IDs or URLs to see if they are truly the same object or two different components.

Cheers,
Tobi

[Martins de Lima]

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

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

Tks

[Tomislav Tobijas]

@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

...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 👀