We have several changesets that got linked in the past to JIRA issues. Doing them one at a time with named reindex feature isn't practical. How would I rerun the index from an initial changeset number to refresh all of the links?
So by 'quite some time', can you quantify that a bit more? When I restarted JIRA, the reindexer ran, but only got through the first 100 changesets. Doesn't seem to have ran again after that one time (8 hours ago). The RevisionIndexService is set to the default delay of 0. Scan Rate and Max Files Scanned properties are out of the box.
Tried the Force Run to no avail. Is there something I'm missing in tuning this? We are on TFS 2012. Please advise on our next course to get the remaining changesets
OK, that's for sure too long. I mean in total to rescan all changesets it can take long time (and it really depends on settings, total count of changesets to process, total number of files modified in changesets, etc.). It can take hours, days... but you should see the progress every couple of minutes.
Can you verify that license is OK now? Does the date of last run update (automatically or by force run)? Could you check logs?
Hey Atlassian community, I help lead engineering at Sentry, an open-source error-tracking and monitoring tool that integrates with Jira. We started using Jira Software Cloud internally last year, a...
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