First, question why you think you want to index regularly. You should only need to index when you've been changing certain field related information or when something goes badly wrong. The request for "regular reindexing" usually means you've got a problem somewhere and you're trying to patch over the cracks - it's almost invariably completely the wrong answer.
Hi. The question is "why would anyone want to re-index on a schedule". An answer is that an indexed field is time-dependant. An example of this would be a custom field used to calculate an urgency score based on the current time and the due date. Judge for yourself whether that is a problem and there is a crack somewhere.
That's a perfectly good requirement, but scheduled re-indexing simply tells me that you've picked the wrong approach to dealing with it. Consider it this way - what you're effectively asking for is a count-down clock. That's fine, but constantly recalculating the current value is inefficient and wasteful. Just fix the end point and work relative to that. In your time-dependent JIRA field, you're asking for an "urgency score" to increase on the current time and due date. Wrong approach - given the current time and due date, you can calculate the score already (and if they change, you can recalculate) There is no need for scheduled indexing in JIRA. If you're asking for it, you are either plastering over something that is broken, or you have got the wrong answer to working with time-dependent fields.
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
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