Buying CI minutes for any namespace should never unassociate the paid tier subscription
Problem
When a group is subscribed to a paid tier (Bronze, Silver, Gold) on GitLab.com and has more billable users in the group on GitLab.com than is purchased in the subscription, when the user purchases additional CI minutes the following undesired behavior occurs -
- A new subscription is created for the CI minutes instead of the minutes being associated with the existing paid subscription.
- The group association to the previously purchase subscription (Bronze, Silver, Gold) is removed and the subscription is orphaned.
Steps to recreate
- Create a group in GitLab.com
- Purchase a subscription for any paid tier on GitLab.com for any number of users
- Add more billable users to the GitLab.com group than the number of users allotted in the subscription
- Purchase Additional CI minutes by:
- Navigate to group's Settings>Usage Quotas
- Select Buy additional minutes
- Follow the purchase process to buy any amount of additional minutes
- BUG1: A new subscription is created for the CI minutes instead of the minutes being associated with the existing paid subscription
- BUG2: The group association to the previously purchase subscription (Bronze, Silver, Gold) is removed and the subscription is orphaned.
Proposal
During the purchase of additional CI minutes (Step 4.3 above) in a use case like this, provide the user notice that the group's number of billable users exceeds its purchased user amount and provide option to pay for those users along with the additional CI minutes.
Example Screenshots
Current "workaround"
- Ask user if we can charge the card on their behalf for the additional users.
- Change the namespace to "free" in Gitlab.com admin
- Try associating the namespace with the subscription in the customers portal
- If the system is charging for all users and not crediting for the previously paid users, create an SE issue to see if there is a conflict causing this
- If the system correctly applies the credit, complete the purchase
@lyle investigating console workaround
For more: discussion on slack (internal)
Summary of Support Tickets Affected by Issue
- https://gitlab.zendesk.com/agent/tickets/131493
- https://gitlab.zendesk.com/agent/tickets/132182
- https://gitlab.zendesk.com/agent/tickets/132597
- https://gitlab.zendesk.com/agent/tickets/132437 (GL.com shows bronze, but subscription not showing group, now that it's orphaned gets 404 when trying to purchase minutes for group)
- https://gitlab.zendesk.com/agent/tickets/132240
- https://gitlab.zendesk.com/agent/tickets/132819
- #672 (closed)
- https://gitlab.zendesk.com/agent/tickets/132947
- https://gitlab.zendesk.com/agent/tickets/133110
- https://gitlab.zendesk.com/agent/tickets/133357
- https://gitlab.zendesk.com/agent/tickets/133546
- https://gitlab.zendesk.com/agent/tickets/133573
- https://gitlab.zendesk.com/agent/tickets/136205
- https://gitlab.zendesk.com/agent/tickets/137840
- https://gitlab.zendesk.com/agent/tickets/137791
- https://gitlab.zendesk.com/agent/tickets/138649
- https://gitlab.zendesk.com/agent/tickets/138827
- https://gitlab.zendesk.com/agent/tickets/138976
- https://gitlab.zendesk.com/agent/tickets/138730
- https://gitlab.zendesk.com/agent/tickets/139225
- https://gitlab.zendesk.com/agent/tickets/138707
- https://gitlab.zendesk.com/agent/tickets/141672
- https://gitlab.zendesk.com/agent/tickets/141926
Edited by Gayle Doud

