I can't do much about the UI. Personally I think it takes far too much real estate.

Can I point out you can simplify the rules just by using the range 50000-50059 so you only need 4 rules, TCP/UDP inbound and outbound.

2 in the end
(1 TCP and 1 UDP for the three sets of ports) x 2 for Upstream/Downstream

UPSTREAM
TeamsAudioUUDP
3 All UDP Any : 50000:50019 / Any : All
TeamsAudioUTCP
3 All TCP Any : 50000:50019 / Any : All
TeamsVideoUTCP
4 All TCP Any : 50020:50039 / Any : All
TeamsVideoUUDP
4 All UDP Any : 50020:50039 / Any : All
TeamsScreenUTCP
5 All TCP Any : 50040:50059 / Any : All
TeamsScreenUUDP
5 All UDP Any : 50040:50059 / Any : All

DOWNSTREAM
TeamsAudioDTCP
3 All TCP Any : All / Any : 50000:50019
TeamsAudioDUDP
3 All UDP Any : All / Any : 50000:50019
TeamsVideoDTCP
4 All TCP Any : All / Any : 50020:50039
TeamsVideoDUDP
4 All UDP Any : All / Any : 50020:50039
TeamsScreenDTCP
5 All TCP Any : All / Any : 50040:50059
TeamsScreenDUDP
5 All UDP Any : All / Any : 50040:50059

It seems to have helped though frankly Zoom has no such problems or does not report them

Can I moan gently about the UI though, having two lines for each rule is wasterful and means I can't easily cut and paste the text in to here

deleted as double posted

I've only just updated the docs to put in the section about port ranges and multiple ports. I want to have a go at fixing the Webconfig so you and do the full combination allowed by the multiport rule.

Right thanks for the pointer, I missed it was a ":" not an ",". Now to see if it helps. Its quite annoying as I have a decent home connection of 80/16Mbps and Zoom copes fine without help good to know that Microsoft still can't write software!

And I am learning even more. The UI won't allow combinations of ranges and lists. It seems to take a single range or a list but not both together. I'll file an bug report.

Even that answer is incorrect. It seems you can use anything allowed by the mutliport module in iptables. From the man pages:

multiport

This module matches a set of source or destination ports. Up to 15 ports can be specified. A port range (portort) counts as two ports. It can only be used in conjunction with -p tcp or -p udp.
--source-ports [!] port[,port[,portort...]]
Match if the source port is one of the given ports. The flag --sports is a convenient alias for this option.
--destination-ports [!] port[,port[,portort...]]
Match if the destination port is one of the given ports. The flag --dports is a convenient alias for this option.
--ports [!] port[,port[,portort...]]
Match if either the source or destination ports are equal to one of the given ports.

Use a colon e.g:

1000:2000

but only a single port range per filed so it sounds like you may need 6 rules, 3 upstream and 3 downstream. Please be very careful with your choice of source and destination ports. Generally you only want one of them per rule and what is an upstream Source Port normally becomes a downstream Destination Port and vice-versa.