Ability to enter additional activation code(s) for future subscription(s)
Background
Currently, when a customer has an active Cloud License enabled subscription, there is no option for them to enter a second activation code.
Unlike with a legacy license MY deal, a cloud license enabled MY deal does not generally require a new activation code to be applied at the start of a new year. Thus, there was not thought to be a need for entering multiple activation codes on a single instance.
Problem
For a MY deal created as a single subscription and activated with cloud licensing, with QSR enabled, there is no issue and no need to enter a second activation code. This is the standard scenario. However, often, limitations in our systems/processes require a single MY deal to be setup as multiple unique subscriptions. In these scenarios, a second activation code is generated and would need to be entered in order for the customer to continue to years 2/3/etc. This occurs in the following scenarios:
- Ramp deal created as multiple unique subscriptions
- EoA deal created as multiple unique subscriptions
- MY deal with CL enabled but QSR disabled (scenario also being reviewed separately: customers-gitlab-com#4816 (closed))
See current view, no button to add a subscription, so no way for the customer to activate years 2/3: 
Workaround
Until this ability is added, for customers in this scenario, their options are as follows:
If their future year subscriptions do not yet have activation codes created (created pre-strict cloud licensing or opted out):
- Upload the legacy license key for years 2/3. Once active, Customer can request to move to cloud licensing during years 2 and 3 via Support ticket.
If their future year subscriptions have activation codes and/or are on strict cloud licensing:
- Reach out to sales representative to request a Legacy license. Support can switch the subscription to
TurnOnCloudLicensingtoNoafter Sales get approval from VP, and then follow the above process for legacy upload. -
Wait until the new subscription starts. Delete the current activation code and add the new one. NOTE: this will temporarily downgrade the subscription to free, and then risks an error when applying the new code.Support should apply a temporary license for a customer in the grace period between multi year cloud activated subscriptions. This allows the customer to enter the new activation code without reverting to free.
Proposal
| Task | MR | Status |
|---|---|---|
| Change sync button | !106507 (merged) | workflowproduction |
| Remove manage subscription button, replace with CDot link | !106502 (merged) | workflowproduction |
| Add activation code button | !106492 (merged) | workflowproduction |
| Remaining small UI changes (reordering details etc) | !103983 (merged) | workflowproduction This will be the final pass, so blocking until the other MRs are through to ensure we have all of the changes outlined in the issue |
Add the ability to enter a second activation code on self-managed instances when one has already been applied.
- This should work the same way as the applying of a legacy instance today:
- User is able to enter a new code
- They receive a confirmation pop-up when succesfully applied (or error if unsuccessful)
- The subscription then shows up in the list with date uploaded/starts/ends
