Yo,
I'll just remind you all that a ticket has been made, and although the team doesn't necessarily answer threads all the time, I can assure you we're at least taking a look at them, see how things develop, etc... So, although we can't be on all threads at once, you can at least be sure I'm stalking this one.
The ticket is already made, as I mentioned, and already has not-low-priority set. The reason why there's no quick hotfix/patches for this issue in particular (or others of similar severity), is because the process to create, test, validate and push a version is a bit more complicated and resources-heavy than one might think (although thank the gods we're not on PS4/X1... I'd have jumped in front of train in that case...). I won't get in the details because there's probably an NDA I haven't read somewhere in my contract, but basically, pushing for a patch/fix/release of any kind is trickier than it sounds.
And let's be clear, I'm not trying to *justify* anything, just to *explain* so you can have a bit more visibility... well... as much as I can give at least, he he.
I hear you when you say this bug is annoying, and it's not the only that made it in 2.7.1 (I think there was a wonky AI during crusades thing ; been fixed in our internal versions since at least). If I can convince the pertinent people to have a patch before our next "big" release, that'd be nice and all, 'cause I'd enjoy seeing some issues fixed for you as well, but I cannot promise anything - in the end it's not my decision. So... maybe...
Tho not the news you've been waiting to see, I hope it at least gives *some* visibility on what's going on.
Arthur