Hi guys,
As @Pete already mentioned, it works like this, but we already noticed it’s not optimal:
This is how it already works in our development version, so it should be included in the next version:
I’ll add this report to the existing task and let you know once it’s included