Skip to content

Sorting of pipeline schedules persisted to local storage

  • Please check this box if this contribution uses AI-generated content (including content generated by GitLab Duo features) as outlined in the GitLab DCO & CLA

What does this MR do and why?

Sorting of pipeline schedules persisted to local storage

Sorting was first implemented in !157224 (merged). This implementation was missing a persistent storage of the last sorted state and the user had to restore their prefered sorting by clicking everytime the page is reloaded.

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

  1. Navigate to Pipeline Schedules of a project (http://127.0.0.1:3000/gitlab-org/gitlab-shell/-/pipeline_schedules)
  2. Sort the table by non default value
  3. Reload page
  4. Sorting is the same as before the reload
Edited by Martin Schurz

Merge request reports