I want to schedule the re-index via REST, that's no problem. But I have a question about the parameters:
index change history
What is the exact difference? I don't think I need to set all of them to true, because my main problem is that a changed issue status is not currently displayed in a dashboard, it often still says the old value. So I guess the "index change history" would be enough? I would then run that re-index hourly, and once a week a re-index with the other two parameters? Does that make sense?
If you already heard about Smart Commits in Bitbucket, know that you just stumbled upon something even better (and smarter!): Genius Commits by Better DevOps Automation for Jira Data Center (+ Server...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events