In a Team-managed project, for some reason a browser search action is intercepted and turned into a filter action. This is driving me nuts. When I do a search in the backlog I want it to search, not filter, so that I can find the issue in location context in the backlog. This is a severe efficiency killer. Please fix! It works as it should in company projects. Thank you.
Atlassian support noted for me that Cmd/Ctrl-G (find next) is a workaround. Now to deal with muscle memory until this is fixed...
Sigh. The "Cmd/Ctrl-G" find next workaround does not work in the backlog unless the target is in the viewable part of the screen. If the target is above or below the fold, it doesn't find it. Apparently even if I scroll to the bottom to load all of the backlog, it cannot be found by the browser unless it is in view. PLEASE Atlassian! Give us back Cmd/Ctrl-F!