Tracking issue: Track and increase batch changes merge rate

Created by: malomarrec

Background

The key measure of success for batch changes creators, as well as the platform team lead that champions for Batch Changes, is the number of batch changes changesets that get merged. Making our users successful can be broken down into allowing them to create batch changes for lots of scenarios, and making sure batch changes changesets get merged.

Problem to solve

Our users report that some batch changes never get completely merged, and remain in an incomplete state. This can be broken down into several subproblems:

as the team lead, how do I view the total value that was created (# merged batch changes)
as the team lead, how do I know what batch changes are making progress? what batch changes are stuck? also see https://github.com/sourcegraph/sourcegraph/issues/20738
as the batch change creator, how do I stay on top of all my batch changes and analyze their progress?
as the batch change creator, how do I make sure the target repository owners are aware of my changeset?
how does a repository owner get notified, in their workflow, that the changeset needs to be merged?

Private insights are tracked here.

Measure of success

Increase 1-month merge rate from x to y.

Solution summary

This is pending discovery and UX research Work with Dudley if we create a dashboard that highlights value created on top of tracking and providing actionable ways to get changesets merged.

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

Impact on use cases

This impacts all Batch Changes use cases, and in particular:

Code Health
Code Reuse
Incident Response

Delivery plan

Here are the issues that relate to this and could be good candidates:

Planned work

Legend

👩 Customer issue
🐛 Bug
🧶 Technical debt
🎩 Quality of life
🛠️ Roadmap
🕵️ Spike
🔒 Security issue
🙆 Stretch goal