-
Notifications
You must be signed in to change notification settings - Fork 324
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update draftEnterpriseInvoice
mutation to include the option for not touching Stripe
#9731
Comments
we'll probably need to change the name here because if
i know this is a problem for legacy PPMIs where we don't have access to the DB to update all teams/orgs to enterprise. Moving forward, we set
I see there's some logic for |
I agree!
I think so! Yeah moving forward this should be the preferred solution
I suggested this to sales before but it does not look like a popular option, especially for some gov users (e.g., this thread🔒). I guess people don't like having a deadline to pay/sign the contract. |
talked to Rafa about legacy PPMIs & we can now just directly hit the DB to upgrade them, so the only use case we have to worry about is free trials. The usecase in the chat is a good one! Seems like it's just for pubsec, but now that we're in Platform 1 I'm not sure if we'll ever have to support that since they can just use Parabol in P1. We'll need to confirm this to make sure. Is there a usecase we have for private companies? Providing a way to upgrade that isn't tied to a payment method & doesn't have an expiration feels like a dangerous thing to add to the API. |
We have a couple of use cases where we need to upgrade an org to enterprise but we do not create new Stripe subscriptions:
enterprise
tier but we only need 1 Stripe customer/subscriptionSuccess criteria:
draftEnterpriseInvoice
mutation with an optional boolean argument (default to true)createStripeSubscription
. When sets to false, the mutation upgrades the org toenterprise
without creating subscription in StripeEstimated effort: X points (see CONTRIBUTING.md)
The text was updated successfully, but these errors were encountered: