Genreve_S wrote:It might be worth giving it another go
Genreve_S
Your reply gives me no confidence that support will get to the correct destination that fixes this. We are now up to 3 attempts now with the exact same result (result being - 'known bug, development is aware, nothing we can do to fix it - too bad, so sad, sry')
How about giving me specific key phrases, or even a person in the know, or an internal procedure knowledge base article that the support personnel should follow to get this fixed on the 4th attempt?