Refine the History interface of the package detail UI.

Release notes

Problem to solve

In 13.7, we expanded the Package History UI to include more robust historical data. The MVC of this had limitations including only being able to show 5 of the most recent builds.

Intended users

An user at an organization whose Ci builds many iterations of the same package version.

• Delaney (Development Team Lead)
• Sasha (Software Developer)
• Devon (DevOps Engineer)
• Sidney (Systems Administrator)
• Alex (Security Operations Engineer)
• Allison (Application Ops)

User experience goal

Allow a user to understand not all of the history is displayed by default, and an intuitive way to expand the history to include more historical data.

Proposal

Create a way for users to set if they see a full or condensed history feed for the package. Default is condensed.

UI Proposal

Further details

If the full history exceeds 1000 historical items, even on full view, they will hit the bottom of the history and be presented with a "Load more" option to continue with the next 1000 events.

Permissions and Security

Documentation

Availability & Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

Links / references