Skip to main content

Bulk edit all Stacks on the Stacks page

Feature RequestsUI/UX

The Stacks page is limited to 50 entries per page, limiting the number of stacks to bulk-discard or confirm.

With 350 stacks tracked in Spacelift, I have to perform the same bulk action up to 7 times (350 total stacks / 50 stacks per page = 7 form submissions) to cover all my stacks.

State changes from queuing Stacks on page 1 can lead to issues when attempting to bulk-act on the next pages.

If I am viewing a Stick list with a filter, say everything that has been Discarded, then trigger a new Run, the first few stacks on the first page will change their State, falling out of my Stack List Query. This changes the stacks provided at the end of the first page and the beginning of the next page.

Needing to load the next page means Stacks could be missed in the next bulk-action on the next page.

Problem
Status: ✅ Completed2 comments

Log in to comment and vote

Comments2

  • Natalia Gazda

    Team•

    Nov 28, 2024

    @Adam Jackman, could you please let me know a bit more about this? What would be the use cases?

    • Emerald Milkyway

      •

      Dec 2, 2024

      A common one is when shared code is changed. That shared code isn’t in the regular plan policy to prevent every PR from running 1000+ stacks for PR checks, but once it’s merged we need to run every stack that uses it (which have a unique combination of tags).