Yes, we've found many issues with 5.2.11. Reported to Atlassian support. Had to roll back to 5.2.10. Would advice sticking to 5.2.10 for now. Have seen a few other answers with users report the same.
Hi Brad,
As Harry mentioned, it seems that this is indeed a bug, as there is a KB that talks about it here. There are also steps that can be performed as a workaround, although settling for 5.2.10 is also an acceptable workaround.
Currently the reason this is happening is still unknown though.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.