Not in the UI that I can think of directly.
But the log will have "indexing" lines in it, and I think the admin audit logging will catch it as well, as long as it is enabled.
I'm not entirely sure how much use it might be though - the index is also updated whenever an issue is touched, so technically, the system was partially re-indexed the last time you used it! I'm guessing you mean one of the full re-indexes though (or project re-index?)
Thanks Nic,
I was referring to admin full-index. Will look into audit logs.
S
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @shailesh ligade2 Did you find it on the logs?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Daniel Alonso though you posted this a while ago I figured I'd share the below
Current Workaround
This is from:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you @john morrissey very useful :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Daniel Alonso though I'm not sure I trust that as my JIRA HOME > Cache > Indexes folder has a time stamp of the installation date though indexes inside have newer dates. I'm still piecing it together so will update here with what I find
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I had to look at $JIRA_HOME/caches/indexes/issues to obtain the latest re-index start.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I forgot I posted here. Seems the offline reindex builds and cleans up the older index files but the online doesn't as they're in use so it's good to do the offline once and a while as it will clean up disk space also (at least did for us)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think re-index events are not included in Audit Log (System --> Audit Log), or at least I don't see them and Atlassian documentation don't mention it (https://confluence.atlassian.com/adminjiraserver/auditing-in-jira-applications-938847740.html).
It would be great that this info was included there: re-index type (project or global background/blocking), start and finish.
Meanwhile, I prefer to take a look into log files. It's clear and easy to know when re-index started and finished.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It appears to me that the Issues folder is timestamped with the current date, however, the minimum date of the files within the folder does seem to be the date of the last index. I specifically validated against a background re-index.
It's unclear if the timestamps can be used to definitely identify start/end times of the re-index, but the date appears correct.
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.