Hi All
We have recently planned to migrate our jira to a new server. Now we have prepared a test environment and carried out the migration according to the official documents. Everything is working normally at present, but we found that some data was lost
1. Our database is backed up every day by mysqldump command. We recovered one day's backup to a new database. I can find the corresponding issue in the database, but I can't search it on the web
2. We have been using the scriptrunner plugin and we found that the configuration is missing a lot. The plugin works, but some of the previously configured scripts are missing
In addition, we find that the latest creation date of the issue seems to be 2024.6.14, what is causing this problem( Once jira was up, we refactored the index, but that didn't seem to solve the problem )
our jira software version :8.13.3
If you want to keep all the creation dates, I can recommend https://marketplace.atlassian.com/vendors/1215318/help-desk-migration - it terms of issues data migration, this works best of all I tried
Hi @arno
If issues in the database aren't showing up in the Jira UI, it typically an indexing problem, Although you mentioned that reindexing was done it does hurt to do it again, reindexing using the Lock and Rebuild Index
Also try to check for any database consistency issues that may have occurred during migration. Use the Integrity Checker
Lastly verify your Permissions and Visibility Settings.
Dd
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
thank you for your reply
According to your suggestion, I have checked our index file, there seems to be some problem (the data size does not correspond), and I am currently reconstructing the index, I hope your method is effective
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There is one thing I want to confirm with you, our official environment carried out an index reconstruction in 6.22, midway due to the execution of automatic backup script, resulting in an interruption of index reconstruction, and then we did not index reconstruction of the official environment
At present, our test environment uses many methods for index reconstruction. On the web interface, only the data created in 6.22 is displayed, and the data behind is empty. Is it because of this reason
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.