Thanks for creating it! Let's schedule it for %19.0

groupprovision highlighted that we constantly experience issues with auto-renewals for personal namespace subscriptions. I would like to estimate the size of the problem but there is no way (or at least I didn't find it) to get this information from Zuora reporting.

@aluthra2 could you please help to query the list of current active subscriptions attached to personal namespaces? I think CDot has all the associations needed

cc @tgolubeva

Either we block auto renewal and let them expire naturally or we block them from purchasing new Add ons - both of those things would be within subscription mgmt's purview - Would you agree?

This is correct. I found the old plan Deprecate subscriptions for Personal Namespaces (gitlab-org#6380) to actually stop the auto-renew for these namespaces. We need to figure out the volume of subscriptions first to say if we can just disable auto-renew there.

@ppalanikumar we don't have a particular initiative to tackle this in our Backlog. If we are only talking about the customers in the list above, could we reach out and suggest our help there? Otherwise most of our automated solutions would be more costly than the help to migrate a handful of customers 🤔

@paulobarros I agree, I'd say the plan is:

Confirm if the records are created correctly on adding members in a straightforward way

Option A. If yes, figure in which cases SeatAssignment creation is not triggered

Option B. If no, we have a clear regression case, propose the tech solution or find the historical commit when it was introduced

After figuring out in which Option A or B we are in, let's document the result in this issue. This will help to move iteratively and don't loose the context.

Thanks @faleksic LGTM 👍

@aturinske could you please continue with the maintainer review?

What does this MR do and why?

The branch rules link to a literal ^All branches$ instead of just showing all branches.

This MR fixes that by removing the query literal.

References

Screenshots or screen recordings

Before	After

How to set up and validate locally

The video attached above shows the outcome and how to test.

1. Go to any project
2. Go to settings > merge requests
3. Click on branch rules
4. Click on all branch rules
5. Observe the link

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

@faleksic the change itself looks good but let's also add a small test to cover the updated query 🏓