Skip to main content

Improve Back-Office Navigation UX for Run logs

Feature Request

When investigating a run’s logs, each log view updates the URL and adds to the browser history. This makes it difficult to return to the run overview — you have to hit the back button many times (one per log view). It’s easy to overshoot and end up back at the task overview, losing context and filters.

Using the breadcrumbs on the Run’s log also takes you back to the task overview with filters reset, forcing you to also rebuild your filtered run list.

Suggestions:

  • Avoid pushing log view state to browser history.

  • Make breadcrumbs return to the filtered run list state.

This small fix would remove a lot of friction from debugging runs in the back-office.

Posted by Simon Poulsen ·
4 comments

Comments4

  • An Anonymous User

    •

    Apr 3, 2025

    @Simon Poulsen I’ve just deployed a change so when clicking log items it doesn’t add to the browser history anymore.

    This means you can now go to a run, click around, and hit the back button to go back to your runs list.

    • Simon Poulsen

      •

      Apr 3, 2025

      Amazing, thank you for taking the time to fix this 💪🙌

  • Simon Poulsen

    •

    Apr 2, 2025

    Let me know if this type of feedback should go somewhere else, since it is a small UX tweak. Felt compelled to post it, since it annoys me almost every time I use the back-office. 😅

    • maverickdotdev

      •

      Apr 2, 2025

      This is great feedback! Please keep it coming

      👍