Rather than redesigning the transfers screens to show some sort of truncated summary of completed transfers and free up render time, I decided to implement timer-based expiration of transfers and minimize the data on the screen that way.

This should resolve a major user pain point while I continue to think about how historical transfer data should be displayed.

Note that users need to opt-in to this behavior explicitly, so as not to surprise existing users with new functionality. It may become default behavior at some point, probably the next major version.

From the docs:

Data Retention

Retention of transfer records on the UI (and in API endpoints) is, by default, indefinite; completed transfers will remain visible until they are manually removed. Users can optionally configure time-based retention rules for both uploads and downloads, and can specify different settings for different dispositions (succeeded, errored, and cancelled). Transfers are checked for expiration on a 5 minute interval, and the minimum retention time is 5 minutes.

All retention periods are specified in minutes.

YAML

retention:
  upload:
    succeeded: 1440 # 1 day
    errored: 30
    cancelled: 5
  download:
    succeeded: 1440 # 1 day
    errored: 20160 # 2 weeks 
    cancelled: 5

Closes #963
Closes #962
Closes #899
Closes #761
Closes #393