Compass feature roadmap

[Guy Derriman]

Compass Product Owners: This is more a question for you
I am looking at making a significant investment into compass and onboarding about 125 assets. Whilst we do the automation I want to track uplift/compliance status with Custom Fields. Examples are .net version, azure subscription, isHighlyAvailable. Id like to be able to make scorecards against these values but it is currently very difficult. Id like to commit to compass because I see the potential. 
However there are a few shortcomings and I want to know what the intention is before I commit

• Custom Field: Type single/multi list - fields are not available in Component search, will this be enabled? (can currently select but then not able to select list value)
• Custom Field: Type single/multi list - fields are not available in Scorecard criterion, will this be enabled?
• Custom Field: Type Text - Can only check for not null. However system fields like Repository can have regex as a validation rule. Will there be more complex rules made available on this Custom Field: Type Text?
  
  

Export to Excel: Whilst allowing you to manipulate the data for any reporting you desire. It would allow people to commit to Compass and to store component meta data in Compass. If compass scorecard criterion are not complex enough (yet) you could export to excel then use Excel to tell the story (uplift/compliance etc) instead. Is this on the roadmap? 

[Katie Silver]

Hi @Guy Derriman ! Just replied to you via email. 

If other users also want these features, feel free to chime in here and I'll see if I can get more details for ya. 

[Christopher Graff]

Definitely upvoting:

Export functionality - Having that ability within Compass (rather than like GraphQL) would save tremendous time as we migrate/setup 100s of components in Compass. In our use case we're consolidating several systems, each maintained components differently. Exported we can more easily and quickly review for completeness and consistency.

Custom Field - similar to previous use case, adding additional custom field search ability as well as scorecard usability would greatly expedite quality control and completeness of components. Example: identifying where a person custom field is empty, or RegEx to confirm a custom field for a version number (for example) contains a number.

[rjb8prT5Y]

@Katie Silver I would find a lot of value in all of @Guy Derriman 's feature requests.

[Mike Guta]

@Katie Silver is there a publicly available roadmap for Compass?

[Katie Silver]

Hi @Mike Guta , no we don't have a public roadmap yet. I am not sure when one will be made available but I'm sure we'll post in the community about it when it happens.