Skip to main content

<stack-name> to always be clickable when under a stack

If I’m on a stack tab (1-level deep) there’s a header at the stop like stack <stack-name> and the <stack-name> is not clickable, when I would like it to be. I think it would be reasonable to match when I’m looking at a specific run (2-levels deep) where stack <stack-name> is placed and <stack-name> is clickable and takes me to the stack.

Bouncing back and forth between the back-button and the <stack-name> is a very minor annoyance, but since I’m in spacelift so much, I realize this minor annoyance as a means that I can’t just rely on muscle memory. I would like to just rely on muscle memory to go to a stack quickly. Oftentimes I click the back-button when i don’t mean to, and I’m at the view viewing all stacks, and I have to find the stack again (out of >1000 stacks, I have to search that and it slows down my workflow).

Not sure if the stack main “tracked runs” should be clickable, it would be no-op. I just want to be say on the PRS tab and have <stack-name> clickable.

Workaround
Status: ⬆️ Gathering votes1 comment

Log in to comment and vote

Comments1

  • Black Breeze

    •

    Oct 27, 2025

    I can see how this becomes more pronounced when managing a large number of stacks (>1000 as you mentioned), where efficient navigation becomes increasingly important.

    We're currently mainly focused on features that unlock new workflows and solve broader infrastructure management challenges, but I've logged this feedback for our design team to consider as part of future navigation consistency improvements.

    In the meantime, I’m also opening this to community voting to see if there’s a critical mass required to prioritize this for delivery.