100%
In my prior role I used several different PLC programming tools. One of them had EXCELLENT fwd/back navigation, the others did not. In the departments using the tools without this feature I really struggled to maintain my flow of thought (sic) and often had to stop and go back to the start of the debugging process to find out where I was or how I got there
I cannot stress strongly enough how massively this helps with cognitive load. Once you have it, you dont want to go back. I used to joke and ask my collegues if they would like me to remove the BACK/FWD buttons off their browsers 
In a production environment this is very often the difference between a minor stoppage and a major breakdown.
I have raised this before (but I cannot for the life of me remember where!)
In order for Feature Request to be even considered, we will need a clear set of requirements / expectations laid out (and even then, it is not a dead cert, but its certainly not gonna happen without it) For example:
- How is the feature surfaced? Buttons in the toolbar? Shortcuts?
- On Shortcuts, I would strongly suggest they should have default key bindings set (should be simple and common e.g. Alt+Left/Right)
- What actions push a location onto the navigation stack (e.g. double clicking a node, switching tab, selecting a node, changing sidebar panel, scrolling, page up/down etc.)
- Whether the navigation stack should include taking you back into node edit panels or not.
- etc.
