This is not a duplicate of Can we have a guaranteed pipeline for responses from Stack Exchange?. That specifically refers to high-profile requests that receive a lot of votes, and the answer there addresses that specifically. This, on the other hand, is for more minor things that don't receive lots of votes and views, that the SE team deems of low priority. Additionally, the "response" there refers to a decision and a status tag; this, on the other hand, refers to something to the effect of "we're looking into/discussing this and will make a decision regarding status".
Sometimes, when people post a bug report or feature request here on meta, the SE team decides it's of lower priority, and decides not to respond to it for the time being. More than likely, they place it onto their internal issue tracker and possibly give it a "low" priority.
But from the outset, it appears that such requests are being completely ignored. I'm willing to make the good-faith assumption that each of these requests is in fact being looked at by an employee, who decided not to take action at that time.
Ideally, it would be great if SE opened up their internal issue tracker to the public, to see what priorities the team has assigned to every request, but I can see some issues with that (e.g. "why is my important issue low priority?").
I think it would be great for SE's relations with the community if they at least, for example, commented on each request that gets logged in their internal issue tracker with a comment to the effect of "we're aware of this issue and are looking into it". This way, it's clear to everyone that SE is listening to people on meta. This was an important point in Monica Cellio's Medium post, which said that despite all the internal chat that surrounds an event, it makes it seem like no action is being taken:
I know through internal channels that you’re thinking about how to respond more to all this. But internal channels do nothing for the public record.
Yes, I'm aware that sometimes employees are busy handling things, but a simple comment to this effect takes very little time.