Consider the case where an issue is discovered in a previously archived version. In this scenario, one would want to set the Affects Version field to that archived version. However, archived versions cannot be selected in version picker fields. The workaround is to un-archive the version, add it to the Affects Version, and then re-archive the version. This adds seemingly unnecessary effort that could be avoided by slightly changing the requirements for archived versions.

One possible solution would be to add another section at the end of the Affects Version drop down list for "Archived Versions", similar to "Released Versions" and "Unreleased Versions". Putting this section at the bottom of the list helps keep it farther out of reach, but still allows one to select archived versions if necessary.

Another possible solution would be to allow manual entry of an archived version, without displaying it in the drop down list.

Allowing project administrators to enable/disable selecting archived versions would be a plus.