Ok, that's fine, but it's not "archiving", it's "completely destroying the issues".
You can run filters for "issue last updated before 1st Jan 2017" and then run through bulk-delete for them, but that's only a thousand at a time. I'd script that from the outside, doing it over REST.
JIRA is not setup to archive issues. If you want to remove issues from your JIRA instance but archive them before doing so I would suggest coming up with a process internal to your organization that meets your needs. For example every quarter we do the following:
This provides us with the following:
We have yet to do a full restore to get the information we need. The PDF documents have been sufficient in answering questions that have come up after the project or issue has been deleted.
Hope this helps.
The blog post (written by my colleague) titled How to archive Jira issues on Jira Server and Data Center compares multiple techniques.
If you haven't decided what to do yet, it is a great starting point.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs