Hi @[deleted]It wasn't my goal to talk about every single issue, but in general ... because some of them seems to be trivial but probably no one has noticed the issues ... I know that development is not easy as many users think but when I'm delaying OST deployment in the company for 2nd year it started to be suspicious and my boss is asking "why are you waiting for this solution? There are plenty of them, come and let's buy something working, I'm not paying you for work for OST, you have another duties here ..."And long time ago you've redirected me to the github and since then I'm using github issues.I think it will be better to comment there (github) but ok ...#4030 - but this thread was about old issues, this one if from the same day ... anyway I'm glad that you mentioned this issue because it is nice example how nobody cares. This issue has been reported in July here and folks found the bug (thanks @[deleted]01 for that link). But nobody created the issue on github and bug is still present in the stable a latest release of the product. I think this is waste of people's time when some (like me) have to run into this KNOWN bug (in December), report it, convince others that it is true, found the bug (I'm just stupid user of OST without knowledge of the source code ... so it is a huge waste of time for me because it consumes apr. 20x more time) and then wait maybe months maybe more for release with bugfixes.#3741 ... it is probably some cosmetic issue, I don't care, I'm just doing research and reporting it (for free but I owe this time to my boss) to you guys.#3541 ... good#3540 ... you are wrong, Kevin replied to me but he was just explaining how I get managed some Topic in the selector but this issue from 2016 is about beforeunload and hardcoded strings. And because it is user frontend I think this shall have a priority.#3538 ... Kevin already made a fix (by pull request) ... and please what will be now? The creator of the ticket (me) closes it when PR is solving the issue or better to wait for the merge or proper release or someone else will close this? Ticket is still open.#3537 ... I know my English sucks but if someone will read my text carefully then it is obvious that I'm disabling BOTH parent levels and then the issue occurs... #3207 ... I've made a GIF for you and even found some time a tried to dig into the source code ... I found some reference/clue ... maybe it helpscheers