Hello.
Today in we couldn't been able to see any ticket from our server, when i click on issues it only opens recent ones ( 5 old ones) and not more, o i went back and forth to try and recover the 84 ticket but with no luck, please heelp mee !!!
PS: I don't think they're erased because it shows me the last 5 ones only so at the data is somewhere.
here are some of the tickets.
Hi @Dali,
Looks like the option to run a background re-index is not available to you due to the corruption.
However, you can still run a "Lock JIRA and re-build index". Although this will mean that your instance will be inaccessible to users until it completes.
As a side note, I would recommend ensuring a back-up of the indexes is scheduled. This can be done on the indexing page. Being able to restore to one of these will help if the re-index doesn't solve your corruption.
Regards,
Gary
Thank You @Gary Pasquale and All the rest For your help, I really appreciate it !
I managed to get all of my tickets back by running the "Lock Jira and rebuild Index" .
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I recommend following the steps in this KB: https://confluence.atlassian.com/jirakb/unable-to-rebuild-jira-application-indexes-228623566.html
Since you're already seeing this error that you cannot do a background index, it is possible that you might have to stop Jira and remove the existing indexes you have. This way you can have Jira create a clean index set after starting it again.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Dali
Do a full reindex of the jira instance..
Refer to https://confluence.atlassian.com/adminjiraserver071/search-indexing-802593000.html on reindexing
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.
Hi @Dali
As Gary and Andrew pointed out, do a lock JIRA and rebuild index.
There will be downtime depending on the size of your JIRA instance. But that will fix this problem. Well, not seeing tickets is already a downtime isn't it..
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Fazila Ashraf Yes, it's definitely a downtime for us. Fortunately locking Jira and rebuilding indexes did the trick, Again thanks to all of you for helping
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.