Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Reference to issues in Insight scheme (object) not visible


I moved several insight object types to different scheme and replaced old objects (keys) in existing issues with new ones by using ScriptRunner. Updated issues have been re-indexed and can be filtered by the new insight object keys.

In new insight schema (object) reference to issues is not shown. However, the reference is still visible on old objects. 

If I do manual update on an issue, the reference is updated correctly - visible in new scheme (object).

What needs to be done to repair/avoid this? Is there a re-index function for insight scheme?

Versions:  JIRA - 4.13.4, Insight - 8.10.4


1 answer

0 votes

Insight appears to have some internal listeners that will pick up on the fact that insight custom fields have change and update its internal tracking of the connected tickets.

In my experience, you need to trigger an "Issue Updated" event on the ticket with the Insight custom field somewhere in the event changelog.

This will happen if you manually edit the custom field. But changing other fields don't trigger the connected ticket to be refreshed.

It might be possible to somehow trigger an artificial event using the IssueEventManager. But I'm not sure how you can trick the Insight Listener to pick up on the change and update the connected tickets.

That is may main challenge ... I do not want to update issues since this will add a record to issue history log, and in many cases, trigger a notification or even transition. With additional record in history log I could "live" but notifications and transitions are unwanted. 

I looked in the API documentation for any classes that might control the connected tickets data, but no luck.

Maybe you can ask Atlassian support directly.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events