If you create a single feature request for 20 features it's pretty much guaranteed to be ignored. When we consider a request, and change it's status to "Planned", for example, it means we are planning to do what the task describes. If there are 20 things in the task, and we only plan to do 5 of them, well, you can see the problem.
Now, if the feature request is something like "Add an Affiliate System", we don't expect that to be broken down into every feature of the affiliate system in separate requests. That would be ridiculous. While there may be many parts to an affiliate system, it's a single new feature.
Making 20 changes to an existing feature isn't a single request, it's 20. And that's what we're talking about when we're talking about adding improvements to the Support Manager.
For example, this request - https://requests.blesta.com/topic/support-tickets-add-a-from-column-on-ticket-list-page is very specific, and concise, and it has already been scheduled for development. This is a good example of a feature request.
Thinking about it this way makes it easier for us to look at a request, approve it, create a task for it in Jira, and follow it through to completion.