It’s not a bug - that decision was intentionally made as there was a lot of confusion around the fact that a PurePaths view will only show 100 PurePaths at a time and if you use the PurePaths view to sort by something like response time it lead people to the conclusion that transactions were being missed instead of just not being in that 100 that got included.
Basically the issue was too many users using the PurePaths view to start an investigation rather than being where the final analysis is done if required. Using the filtering options and other analysis views to find the slowest transactions (the ‘zoom in’ feature is especially helpful) can get you to a point where you have only a handful of PurePaths to look through as opposed to trying to sort through 100+ PurePaths.
I’m sure there is feedback coming in that this change can also lead to confusion so perhaps this will change but at the moment it is not a bug.
James