Defect? Basic Users see Change Request Catalogue Items for a newly created Service but not all others (new Service not observing SM Application Setting?)

[Berto2002]

I have the "Network and Infrastructure Support" Service Portfolio item with Change Config on, Subscribers as an OG Type Company and no restriction on the Cat Item visibility; and none of our Basic Users have ever been able to see or raise CRs because we have this setting off:

guest.servicemanager.portal.additionalRequestTypes.change. Allow Change Requests to be raised through the portals using Catalogs and allow all existing Change Requests with a customer associated with them to be visibile [sic] in the portals.

I created a new Service called "Liquidlogic Childrens System (LCS)" with Change Config on, Subscribers as an OG Type General and no restriction on the Cat Item visibility; and the Basic Users CAN see and have started raising Change Requests.

Infra and Network:

User in one of those Companies sees this on portal (no Change item):

LiquidLogic Service config:

User in the LCS Users Subscriber list sees this on portal (DOES SEE Change item):

It seems to me that the new Service is not observing SM Application Setting (guest.servicemanager.portal.additionalRequestTypes.change) which should be preventing Changes from being seen on the portals. All our other services are and have been since launch 3 years ago.

I tried adding the Subscriber OG Type General to the Network Cat Item but that did not trigger the same issue.

I have worked-around this by altering the visibility settings on the catalog item but we need to understand this going forwards.