You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Our client uses Jira Service Management 4.20.11 (Data Center) with multiple nodes. As it turns out very often when you select some Insight objects on some Jira tickets everything works fine only on one particular node that change has been performed on. But on other nodes, when you look from an Insight object point of view, you cannot see that the object is being used on Jira tickets (usually not all of them but some of them is enough to cause trouble). We use Insight automation rules to update or even create Jira tickets for some Insight objects, and when the script can't find a proper ticket, it creates one or can't update an existing one that should be updated. A lot of mess :-/
Reindexing Insight fixes the problem. But obviously, you cannot reindex whole Insight every time someone puts an Insight object on a ticket ;)
But if you could reindex just one object… oh, that would be a great workaround that could be placed in every crucial point of the process (until Atlassian fixes this bug).
I couldn't find any REST endpoint to reindex just one object. I also couldn't find any groovy method that could be used to do that using ScriptRunner.
If anyone knows any working workaround, it would be very helpful!