Affects Version: mandatory checking and archived versions
We implemented the mandatory checking on the field "Affects Versions" to make sure a version must be provided when the issue is created, and it's not allowed to change to make it well tracked.
If we have one version named as "VERSION001", and we have an issue "TICKET-001" which was created in this version. But before releasing to customer, this issue was not able to be solved. Thus, it was postponed to next release, so now the Affects Version = VERSION001, and Fix Version = VERSION002.
Then VERSION001 was released to customer with a restriction TICKET-001. and the version was archived.
In next version VERSION002, when we want to re-visit the issue TICKET-001, things become weird. Since Affects Version is mandatory, and VERSION001 was archived, the TICKET-001 can never be able to edit anymore, because the archived version will not be regarded as the value of Affects Version.
so, my question is, how to include the archived versions when performing the mandatory checking?
