[Search bar] Going back and forth in the browser history does not work.

[luk-kaminski]

[Search bar] Going back and forth in the browser history does not work.

Expected Behavior

From Test Quality, "Search Bar -> Changed search bar controls are reflected in the current URL ..." : Going back and forth in the browser history changes the controls for timerange. Going back and forth in the browser history changes the controls for streams. Going back and forth in the browser history changes the controls for query input.

Current Behavior

Going back does not change anything. There is a feeling that URL flickers for a moment, but eventually the URL stays unchanged. One cannot go forward in the browser history.

Possible Solution

?

Steps to Reproduce (for bugs)

Follow the steps from Test Quality, namely test case : "Search Bar -> Changed search bar controls are reflected in the current URL..."

Context

Test day.

Your Environment

test-dev-ng.dev.graylog.cloud

• Operating System: Linux Mint
• Browser version: Firefox 136.0.1 (64-bit)

[ML-Marco]

Is this going to get fixed any time soon? This should be treated with high priority. If I select a shorter time range in the time line via mouse and want to go back to the previous view it doesn't work at the moment. This is a very common way of using Graylog. Please fix it asap.

Confirmed to not working in 6.3.5.

[T3rm1]

@sethgraylog @luk-kaminski This issue should not wait for someone to fix it on a test day. It breaks Graylog. I'm kinda surprised there are not more people complaining about this. Being able to nagivate back is very crucial. This bug worsens the user experience a lot. Please consider fixing it sooner.

[kmerz]

We plan to work on it now in the near future. I agree that this is a crucial issue that disturbs the workflow.

[ML-Marco]

We plan to work on it now in the near future. I agree that this is a crucial issue that disturbs the workflow.

Will it be part of Graylog 6.3.7? I saw that it didn't make it into 6.3.6.

[linuspahl]

@ML-Marco @T3rm1 We're currently working on fixing this bug. We could simply restore the previous behavior, but we'd like to hear your thoughts on what the ideal behavior should be.

In previous versions, using the browser's navigation controls on the search page affected the search query, time range, and stream selection. When navigating, we would immediately re-run the search, similar to opening the URL directly in a new browser window.

1. Would you prefer that, when using browser navigation, we only update the search bar form values and not automatically re-run the search? This would prevent starting (and potentially canceling) multiple searches when going back and forth several steps at once.
2. Am I correct in assuming the search undo/redo buttons don't help in your use case because they also affect things like created widgets, whereas you only want to adjust the applied filters?

[ML-Marco]

I prefer the old behavior. What I do all the time is "dig deeper" into the results by selecting a smaller time range. If I use browser back I'd want to see the previous results with all filters updated. To 1: Re-run the search. To 2: Navigating back should only change the applied filters.