Hello SergeiRusetski,
Thank you for reporting this and providing steps to reproduce.
We’ve been able to reproduce the issue on version 2.6.1 and can confirm that this is a bug. The issue will be fixed in one of the future releases. We’ll make sure to update you here as soon as the fix is available.