Apply history menu

Created by: sourcegraph-bot

Motivation

We want to enable long running batch changes, that are frequently re-applied, as a step in serving the recurring batch changes use case.

Roughly half of customers think of Batch Changes this way: a tool to enforce rules.

Problem

Changesets accumulate in a batch change, clutteing the GUI. This creates the following issues:

• tracking progress of a long running batch change is painful, as the changesets related to several iterations are in the same view (or achived)

• the burndown chart becomes bigger and bigger, and dilutes the newest apply in the history of all bacth changes apply

• when a user applies a batch change, then realise it is mistakken, the archive will get cluttered.

Proposal

We introduce an version of batch changes in the GUI. Each apply has a version.

• I can view a history of apply, and the related changesets status

• I can view progress by apply iteration (burndown chart and statistics)

• I can apply bulk actions on the changesets of a given iteration (merge, close, detach, sync)

• I can download the specs related to a version

  • note that the specs do not necessarily change at each version: the delta can also come from the on query returning new repositories, or from previous changesets being closed then reopened

Inspiration could be taken form Terraform Cloud and the Kubernetes dashboard that has similar concepts. See screenshots