We recently had a case where a developer was able to select an Archived Release in FixVersion.
This should not be possible and attempts to reproduce the problem were not successful.
He was unable to remove the incorrect FixVersion value, because the release was archived, which is proper, expected behavior. (We know how to correct the problem on the ticket).
We also had similar situations reported to me anecdotally and I have been watching for this... but since it is only done by error, the cases are few and far between,
What I want to know is, has anyone else has seen exceptions like this where an archived release was able to be selected and applied to Affects Version or Fix Version.
