Hey Youbekay! This is a known issue, and we'll be resolving it next patch, but due to the impact of the current state of the live game, and impact to future development, we think we can make a better experience by focusing on current bugfixes and feature work for the upcoming patch instead of using those same resources to get a fix out for this specific issue now.
We know it sucks, and we've added additional test coverage to some of our test suites to ensure we catch this particular issue in future builds, but we feel like the risk to stability outweighs the value we'd provide to players. But we'll have it fixed during the next planned patch!