Quote Originally Posted by jackjones View Post
It's still not fixed. Which release will this be fixed in ?
Unfortunately we did not have enough time to get this in to the most recent release. This is why we normally don't give estimates. In fact, I think DNB misunderstood the milestones system when he replied and said it would be in the next release. It is still on deck but it is assigned to a 'backup milestone' and not the actual 'next release' milestone so I can not promise it will be in our next release. I will add a comment to the ticket to remind management and the developers how important this is. Depending on the workload it might make it in to the next release but it might not make it in until the release after the next release so I apologize for any confusion caused by previous posts.