Please take a look at this and see what’s happening:
I undersand that with the tracker curfew, there’s pressure to close as many bug reports as possible. However, the ‘feature request’ proviso has been turned into an excuse to close perfectly valid bug reports.
“As intended” is not a useful benchmark because intention is predicated on devs having thought of everything ahead of time. Please change the policy so that features should always work “as reasonably expected” instead.
If it’s not possible to immediately fix the bug for whatever reason, that’s fine. Consider just leaving it open with a low priority, or marking it as a known issue/todo. Perhaps, if suitable, add it to the quick hacks list for beginners to pick up.
If you truly have no intention of ever fixing the issue, at least mark it as a ‘won’t fix’ and state clearly that it’s too hard, too complicated, too burdensome, the original author is not available or that the expectation is just unrealistic. At least that’s fair and honest.
But closing the bug report outright as a “feature request” (when everyone knows it isn’t one) is highly demoralizing for reporters, sours your relationship with users, and also just means someone else will report the same thing down the line.