Currently, when issues are archived within Jira, they are not placed into the normal operating search index. While efficient for operations, this does limit the ability to search through the archives. It can be painfully slow when there are tens and hundreds of thousands of issues.

Steps to Reproduce

1. On a large Jira DC instance, archive 20,000 or more issues
2. Try to search for an archived issue
3. It will be painfully slow and in some cases impossible to search

Expected Results

Although it may not have been included in the design, it would be nice to have a separate index created when archiving issues. Given the nature of archived issues, this could be a separate index created on a schedule that does not require daily reindex

Actual Results

It appears that archived issues are not indexed, and searches can take an unacceptably long time to return items.

Workaround

Currently there is no known workaround for this behavior.

Suggestion

If there were a separate index and schedulable task to create an index once issues have been archived, it could make locating these issues easier for gathering information when required.