When creating a ProForma form with a multi-select dropdown linked to the Fix Version/s Jira Field, the dropdown populates with every Project version, including Archived Versions.

In Jira Projects with many Versions, this creates a cumbersome process for users to fill out the form and creates data integrity issues as they may select an Archived version.

Allow more configuration options for the choices when building a form so that Admins can choose if Archived Versions are displayed or not.

Workaround

Currently there is no known workaround that fully addresses this behavior at scale. The following partial options exist but each carries significant limitations:

• Delete the component instead of archiving it — Deleted components will not appear in the ProForma field. However, deletion is permanent and will affect all existing issues that had that component assigned. This is not recommended for most environments.
• Replace the linked field question with a manual multiple-choice question — Switching from a linked Jira Components field to a manually maintained multiple-choice list allows the admin to control which values appear. However, this requires manually entering and maintaining every choice, provides no dynamic sync with Jira, and is not viable for projects with large numbers of components (400+ in at least one known case).
• Native JSM request type field — The native Jira Components field on a JSM request type (not a ProForma form) correctly filters archived components on the customer portal. If ProF