The user's job is to express the problem/request unambiguously. When you understand what's it about, you can rewrite the title in whatever way you prefer. A request shouldn't get invalidated just because the title says "BeatBox doesn't do X [but I need it]" instead of "BeatBox should do X".
Also, we didn't have a policy on this last time I checked, and I saw different developers preferring different ways of titling bug reports... so, as a user, I can never guess which one to use.
The user's job is to express the problem/request unambiguously. When you understand what's it about, you can rewrite the title in whatever way you prefer. A request shouldn't get invalidated just because the title says "BeatBox doesn't do X [but I need it]" instead of "BeatBox should do X".
Also, we didn't have a policy on this last time I checked, and I saw different developers preferring different ways of titling bug reports... so, as a user, I can never guess which one to use.