Server-side batch changes Beta Phase

Created by: jyavorska

Problem to solve

For the Beta, unblock leading tech organizations.

• Unlock large enterprise Batch Changes use case.
• Allow for a smooth user flow, starting with a search (or another feature) and ending on a batch change

Measure of success

• 3 customers create more than 200 changesets server-side
• 2 customers GA running batch changes server-side internally
• One customer agrees to quote / case study

Solution summary

• Scalability (10,000 changeset scale)
• SSBC UI and editor is mature enough
• Feature is fully documented
• We have defined an upgrade policy and have a docs page for it

Out of scope

• Managed executors are out of scope. Only self-hosted executors are inn scope

Artifacts:

• PD 26 APPROVED: server side batch changes

What specific customers are we iterating on the problem and solution with?

• https://github.com/sourcegraph/accounts/issues/580
• https://github.com/sourcegraph/accounts/issues/565

Impact on use cases

This makes using Batch Changes for code health, fixing security vulnerabilities, incident response, and code reuse much easier at scale. It's also a key part in enabling having a one-click batch change from a library

Delivery plan

• Deliver engineering milestone "EM3" tracked in #22764 (closed)
• Release brief (target customers, Q&A)
• PMM material: demo video, GIF, tweets @malomarrec to sync with @danielmarquespt
• CE training session @malomarrec
• Train and handoff first-line support to customer support cc @chrispine