There is a knowledge base article titled Archiving a project that you may want to review. In addition, here are some posts with some suggestions the Community has used:
The idea we have is to archive old issues from PROD server so that the load from the server is reduced for better performance on server.
Also, the archived issues should be accessible to users at any time if they need with the same ID's and data.
When we try to archive issues by moving them to other project, the key gets changed so that does not look helpful.
Any suggestions please.
Thanks and Regards,
Tanishka S Chotwani
>Also, the archived issues should be accessible to users at any time if they need with the same ID's and data.
That completely obviates the point of an archive. Your best option is to simply put them in a state where they can't be updated.
If you want to move them out to another server, then you'll need to find or write something that can scrape out issues and duplicate them in an "archive" JIRA. This is something Atlassian looked at when they first started to work on Data Centre, but abandoned as it was looking like a bigger task than Data Centre itself.
Can a new-to-agile team survive and thrive in a non-agile culture? If so, what advice would you give to those trying to be agile in a non-agile culture? What's the key(s) to success? Share your thoug...
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