The point is that between VLANs, normally the traffic can be only routed, not switched, so none of the L2-related settings (neither /interface bridge vlan-filtering nor the use-ip-firewall... items of /interface bridge settings) have any effect on it. /interface bridge vlan-filtering is used to control membership of bridge ports in individual VLANs (and dropping, on each port of that bridge, of ingress and egress traffic of all VLANs of which that port is not a member), whereas the topic title mentions explicitly routing and you've also mentioned firewall filter rules blocking traffic between VLANs in the text.
So I've asked for the actual configuration, and yes, I was a bit sarcastic because too many people here expect other people to mysteriously find the mistake in a configuration they haven't seen. You may find this common frustration manifest in various ways here, because you have to be creative when asking the same thing all over again. And the final stage is to simply ignore this kind of questions.
I am in accord with @mkx - it may well be your current configuration has solved the issue, however it is quite likely that your RouterBoard is spending more CPU on the task than actually necessary. Or maybe you actually need to filter traffic between two external devices within the same VLAN, but even if this is the case, better-suited tools exist than use-ip-firewall....
BTW, when using CAPsMAN, you don't need to use VLANs at all in some scenarios - in particular, where no L2 interconnection between wired ports and wireless interfaces is required and where all the traffic of the clients of the cAPs is routed at the CAPsMAN device (i.e. no local forwarding, L2 or L3, is required directly on the cAPs).
So all in all - so far the benefit of this topic for the forum community is zero or less. You have provided insufficient and confusing information about the initial issue, I was sarcastic above your tolerance threshold (and I've sent that response with such a delay that the only noticeable part remained the sarcasm because @mkx has asked for the same but neutrally in the meantime), @Anav has just complained about a person who didn't even take part in the topic, and as a final product we have here a topic which does propose a solution to people coming here via keyword search, but it is most likely a solution of something else than the topic subject.
So shall we try once again and better from the beginning or shall we let the waters close over it?
Instead of writing novels, post /export hide-sensitive. Use find&replace in your favourite text editor to systematically replace all occurrences of each public IP address potentially identifying you by a distinctive pattern such as my.public.ip.1.