Any chance that this bug will be addressed in the next iteration? It is giving my testers a lot of trouble... Jon