Based upon this Slack conversation, RHACS 3.73.0 and 3.74.0 will include breaking changes to the undocumented & unsupported GraphQL API, which some of our customer's do use. 

In the Slack conversation, mdarwatk@redhat.com stated:

"On a side note, it would be a good opportunity to understand what do the customers use the graphQL for and to determine possibilities of catering those needs through Trends and Metrics feature which is under discussions."

and rh_nchander commented:

"...but we encourage them to engage to figure out what they actually want so that we can provide a supported solution."

In light of this, creating this Jira as a capturing spot for customer use cases.   The process will be:

1. Public knowledge base article will be published describing breaking changes to GraphQL API, and it will include a reference to this Jira.  
2.  If customers want to express support for this Jira and / or describe use cases, they will open a Support ticket with this information, and the support engineer will add the customer information to this Jira, and then the ticket will be closed.