I get that here too!
The last one took two weeks to get approval from the change committee to fix what they broke
Very frustrating

We get the same here .. something which was working gets broken in the release and when this is discovered, users have to wait until the next release for the fix because we do not do hot fixes unless the business is broken.
We have had an issue for months now for which I have been begging for a permanent fix because I have to manually fix the multiple tickets a day with that issue. It does not matter that both the users and myself are frustrated, because they are not having to deal with the tickets, the Development Team are in no hurry to find a solution.
When I mentioned it again yesterday, I was told "it just keeps slipping back a sprint or two unfortunately" and "only workaround I have for you guys at the moment is hunkering down in the feedback bunker"

I have a workaround of my own .. assign the incoming to the Development Team! If they had to constantly fix them I am sure the resolution would magically catapult in to the next sprint!
