Admin UI inconsistency - adding related list 360 sections - looks at API object name instead of obje

Related products: None

Noticed that the Reports 2.0 and Rules Engine both search on the Object Label when selecting the source object - however, when adding a 360 section, it searches for the API name - this came up with the Opportunities Product object (API name OpportunityLineItems) for Glassdoor. Usually people don't notice because the API name is almost exactly the same, but it stands out as an inconsistency for people working in RE and Reports 2.0.  Can the 'Add 360 Section' related list dropdown behavior be made to look at object label as well for consistency sake?
This is definitely something that ties to overall impression as well.  Key that we always use the Label and not the API name in the Admin interface.
Thanks for the feedback. We will add this to the product backlog