Prevent workflow changes from impacting archived issues

Issue Summary

Archived issues are considered when publishing updates to a workflow to ensure changes to statuses and other properties are taken into account. This is helpful to maintain the correct statuses for archived issues but carries workflow dependencies and may have a performance impact with a large number of archived issues.

These changes could be made during the unarchiving process to prevent a performance impact and workflow restrictions.

Steps to Reproduce

1. Archive an issue
2. Edit the project workflow (e.g. status names, etc.)

Expected Results

Workflow can be edited without consideration for archived issues.

Actual Results

Any updates to the workflow are dependent on the status of archived issues. For example, removing a status that is only applicable for archived issues provides the following message:

We can't remove this status for you
There are issues in this status that need to be moved to another status or project before we can remove this status. Please contact your Jira administrator if you need assistance.

Workaround

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