Description of problem: Once the Swatch is not checking the whole list of SKU's that we have currently, the threshold gets wrong, and hard to explain why the value is far far away from the subs that the customer has. We will add here all the cases that are causing issues/doubts/questions regarding Subscriptions/Swatch and Threshold. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. Use an account that has a subscription that is not in the whitelist 2. Check the swatch 3. Actual results: That subscription/(sockets for that) will not be counted Expected results: create the sockets reference for that subscription and count/display in Subscription Additional info: Definitely, removing the whitelist from this process and allowing Subscription to consume the whole list of SKU should be the best approach here. Maybe, creating a list/information of subscriptions that are not yet counted properly. However, the customer will be able to track/see all the subs that Subscriptions is checking/looking for.
This bugzilla has migrated to Jira and is awaiting prioritization by Product Management. Please reference the attached Jira to continue tracking the issue comments and status.