Issue Summary

When selecting an archived version from Affects version field, it's causing an error as below because the version has been archived, or the archived version is no longer visible in the list. 

This is an issue because Affects versions is meant to be contain the version in which a bug or problem was found. Although it can be useful for tracking problems, it isn't used very often in Jira. Ref: Difference between Fix Version and Affects version

Scenario A: Version is still visible but cannot be selected

Scenario B: Version is no longer visible to be selected.

Steps to Reproduce

Scenarion A:

1. On the Release list page, create a version (Let's call this affects version 2.0) with a start date and end date of your choice. 
2. Create a bug issue type (contains Affects version field) and open it in a new browser tab. (Let's call this issue A).
3. Check the Recent Versions and Unreleased section of the Affects version field and you will find the created version. (Do not refresh this page.)
4. 
5. Go back to the Release list page and archive the created version.
6. Go to issue A's browser tab and select the archived version from the Unreleased Versions section of the Affects versions field. 
7. 
8. It will return an error because the version has been archived.

Scenario B: Version is no longer visible to be selected.

1. On the Release list page, create a version (Let's call this affects version 2.0) with a start date and end date of your choice. 
2. Archive the created version.
3. Create a bug issue type (contains Affects version field) and open it in a new browser tab. (Let's call this issue A).
4. In the Affects version field, look for the archived version, but it's no longer visible.
5. 

Expected Results

The Affects version field should allow the selection of archived version based on its definition below: (ref: Difference between Fix Version and Affects version)

Affects version is the version in which a bug or problem was found. Although it can be useful for tracking problems, it isn't used very often in Jira. 

Actual Results

The Affects version field is not showing archived versions. 

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available