This is stopping users from getting their work done, so I think with our current priorities it counts as Critical. It's just that it's been critical for long enough that we don't complain much about it any more.
A lot of the work in translations import queue review (for projects) is now about templates that should have been approved by the branch auto-approver or perhaps the build auto-approver, but for one reason or another, weren't.
This can happen for instance if the approver can't come up with a unique name for a new template, or when multiple templates get moved or renamed simultaneously and the approver isn't sure which upload goes into which existing template.
Unlike the classic auto-approver (which is applied by the translations import queue gardener), the branch and build auto-approvers know when they are presented with a complete, self-contained unit of work and could report somehow that they ended up with an un-approvable situation. We could add an Unapprovable state, for instance, which calls on project owners or translations admins to fix the problem e.g. by updating the paths of the existing templates.
This is related to bug 531227