I also used to think that way. But in my current team we have lots of components that are maintainerless and attentionless since their maintainer left the team

I also used to think that way. But in my current team we have lots of components that are maintainerless and attentionless since their maintainer left the team for another job. When he hwas still active we all considered this component important because many hours of work where flowing into it. Now it's not maintained, receives nearly zero work, and still the impact to the team and sales is not visible. One could say finding out which components are critical should be someone elses job, e.g. the manager's. All true, but still I wouldn't want to end up spending the prime time of my day for multiple years on a piece of software that nobody uses and nobody makes money with. So I'd argue that I as a dev cannot interact with just the bug db. I need to see what sales is doing, product management, join meetings, etc.