Skip to main content

Single-Operation Filtered Searching

Feature RequestsFilters

We would like to be able to add a filter to that search bar up in the top, similar to drifted:true or similar, which would let us perform single-operation searches for stacks - for example, prod drifted:true , which could give us a list of stacks matching "prod" AND in a drifted state.

Status: 🗑️ Archived3 comments

Log in to comment and vote

Comments3

  • Natalia Gazda

    Team•

    Jul 16

    Hey, thanks for the suggestion. We're archiving this one for now. It hasn't picked up much interest since it went up, so it isn't on our near-term roadmap. Archiving isn't deleting: the request stays on record, and if it gathers more votes or comments we can bring it back. If it still matters to you, add a vote or a comment so we can gauge the demand.

  • Black Breeze

    •

    May 10, 2025

    Thanks for sharing this—super helpful to see.

    We’re actively exploring how to improve the run history and operations surfaces, and filtered search is one of the ideas on the table. That said, we’re pausing to ask: is filtering by operation type the most useful way to help users get what they need?

    From what we’ve seen, the job isn’t always “find this exact Apply” or “only show Drift checks”—it’s usually something higher-level, like “understand why this environment looks wrong” or “trace what changed and who changed it.” In those cases, a filtered list helps, but may still fall short of delivering clarity.

    One path we’re considering is AI-powered. smart filtering. The goal is faster insight with less cognitive load—especially in noisy or high-pressure situations—without making users learn a new query language or vendor schema.

    So we love the spirit of the ask, but we’re weighing whether traditional filtering is enough—or if there’s a better way to help users get what they’re really after. If you’re open to it, we’d love to hear more about the last time you wished this existed. What were you doing? What made it hard? That’ll help us shape something that nails the actual job, not just the interface.

    • Jade Grape

      •

      May 12, 2025

      A (not so) hypothetical use case would be “we made a change to our RDS module and need to check the drift status all of our various RDS stacks, starting with nonprod (since they’re safer to apply)”. So we’d want to search for something like 

      tag:rds AND drifted:true

      Or some logical equivalent.

      That’s not to say that a more organic/smart filter (for example, having a toggle to automatically drill down to “only drifted” or “needs attention”) wouldn’t be useful - quite the contrary, that would potentially allow for similar flexibility.

      Glad to hear that this stimulated some thought and discussion.