Scorecards showing spurious nones

[Oli]

I've noticed that all of my scorecards show that there are 3 components in the None category, but when clicked through, or when looking at the components individually there aren't any.

[Tomislav Tobijas]

Hey @Oli ,

Does this happen only for "None" category/level or for each one? I've just tested this, and it seems to be the caching issue Alexander mentioned, specifically, a browser issue.
For example, I'm mostly using Brave, and each time I select the filter for Scorecard status, it loads the results briefly and then reloads the section, displaying that there are no matching results.

After that, I've tried using a different browser (Chrome), and I've also tried an incognito window in Brave > both of which displayed results as expected. 👈

Can you maybe try clearing the cache or switching to a different browser just to see if it will work? 👀

Cheers,
Tobi

[Alexander Nilsson]

Hi Oli,

what you’re seeing is most likely a known caching or indexing issue in Compass’s scorecard summaries.

The “None” category in the scorecard dashboard represents components that Compass believes don’t have a scorecard assigned or haven’t been evaluated yet. Sometimes, after recent updates to scorecards or component metadata, Compass doesn’t immediately reindex all items so even if every component now has a valid scorecard level, the summary can still show a few entries as “None.”

A few things you can try

1. Force a refresh by toggling the active filters (e.g. switch to a different label or owner team, then back again).
2. Open one of the components from the “None” category directly and confirm that a scorecard is indeed attached. This often triggers Compass to update the index.
3. Check for recently deleted or renamed scorecards - components previously linked to them may appear as “None” until the index is rebuilt.

What’s happening

• The summary visualization uses cached component status data.
• The component list view queries live data, which is why it correctly shows zero matching components.

If it persists for more than a day, I’d suggest opening a ticket with Atlassian Support so they can trigger a backend reindex for your workspace:
https://support.atlassian.com/contact

Hope that helps. 

Greetings,

Alex