Is there a better way of getting a breakdown of component counts by type (or other attribute) than filtering by each value and copying each number of results to a spreadsheet? This could also be useful for: * lifecycle stage * tier * team * project* * single-select custom fields * has / does not have repository * has / does not have label * has / does not have mapped API specification* * using / not using config-as-code* * I don't think these ones can be done via filtering either?

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Component catalog breakdown by attribute

Keith Furnell

Is there a better way of getting a breakdown of component counts by type (or other attribute) than filtering by each value and copying each number of results to a spreadsheet?

This could also be useful for:

lifecycle stage
tier
team
project*
single-select custom fields
has / does not have repository
has / does not have label
has / does not have mapped API specification*
using / not using config-as-code*

* I don't think these ones can be done via filtering either?

Accepted answers

Keith Furnell

Answering my own question: one basic approach, thanks to the inclusion of matches in the smart-link presentation of search URLs, is to build a Confluence table with URLs for each value:

Tier Breakdown.png

Note: That however that search query numbers can sometimes be zero - see https://community.atlassian.com/forums/Compass-questions/Bug-Search-smart-links-show-zero-component-counts-in-many-cases/qaq-p/3025702, or include archived components - see https://community.atlassian.com/forums/Compass-questions/Embedded-Compass-component-search-query-inconsistent-component/qaq-p/2977084

All comments

Sebastian Hesse_7i9tak

Do you mean you go to the components overview, filter for one attribute, then copy the component count, filter the next attribute, copy the component count, and so on? I don't think there's a better way than using the regular user interface at the moment. You could write a custom script using the GraphQL API though.

Maybe as another idea: Would it help if you export the components to a CSV file / spreadsheet and do the filtering/analysis then?

Jeff Madison

Being able to filter the component list by those three items you have an * on would super useful. I have felt that pain, too.

Keith Furnell

Do you mean you go to the components overview, filter for one attribute, then copy the component count, filter the next attribute, copy the component count, and so on?

Yes, clearly not ideal! The resultant filter URLs do provide a dynamic results count when pasted into other Atlassian products, but unfortunately the numbers aren't always reliable.

Would it help if you export the components to a CSV file / spreadsheet and do the filtering/analysis then?

I guess, but that would obviously not be synced and would defeat some of the object of moving component meta data into Compass. The tool seems to have pretty good visualisation around metrics and scorecards, it just seems to be missing an equivalent of Jira's project Summary page with high-level stats.

Keith Furnell

For anyone after a breakdown of components by component type in particular, this is now available via https://myinstance.atlassian.net/compass/settings/component-types. Like quite a few tables in Compass, it's bizarrely unsortable.

Keith Furnell

Answering my own question: one basic approach, thanks to the inclusion of matches in the smart-link presentation of search URLs, is to build a Confluence table with URLs for each value:

Tier Breakdown.png

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

compass